Situation:  I have a website that is ASP.  I put all of my functions in 
an "include" file, then include that file at the top of all of my pages.  
My asp file calls functions from this include.  (I just wanted to have a 
single location for all of my procedures.)

My question:  Is this the best way to do this, or should I split this file 
up and only put in the functions that each individual asp file needs?  Is 
there a performance hit for declaring these functions and not calling 
them, or does the extra text that the server reads does not really make a 
difference?

Thanks!

Ben

Most of my sites are small to mid-size (traffic and content) and
that is exactly how I do it. As a matter of fact, I "functionize"
everything.
An average page looks like:

<!--#include file="incGlobal.inc"-->
<%ThisPageContent%>
<!--#include file="footer.inc"-->

"ThisPageContent" is a function built around the content
of any give page which includes DBConn, SQL query and
everything else.

I also, typically, write an HTML formatting set of functions
that I include at the top of my Global Include file. I'm sure
that there is a sever side performance hit but I have never
experienced a problem.

-----Original Message-----
From: ben.trimmer@e... [mailto:ben.trimmer@e...]
Sent: Friday, May 17, 2002 8:06 PM
To: asp_discuss
Subject: [asp_discuss] ASP Include file


Situation:  I have a website that is ASP.  I put all of my functions in
an "include" file, then include that file at the top of all of my pages.
My asp file calls functions from this include.  (I just wanted to have a
single location for all of my procedures.)

My question:  Is this the best way to do this, or should I split this file
up and only put in the functions that each individual asp file needs?  Is
there a performance hit for declaring these functions and not calling
them, or does the extra text that the server reads does not really make a
difference?

Thanks!

Ben