You will probably actually save performance by using the includes. Once the server grabs it, it will use the cached version until it is changed. Once you modify the file the server will pull it from the disk again. I use includes extensively and I have never really noticed any performance issues. Some of my pages have 6 or 7 include files in them depending on what I am trying to accomplish on the page. Mike -----Original Message----- From: Jeremy Weiss [mailto:jweiss at cei.net] Sent: Wed 7/17/2002 12:19 PM To: Thelist Cc: Subject: [thelist] using #include One of my asp pages is timing out everytime someone hits it, so I'm trying to break up the processing across a couple of pages. I'm looking at the print out of this page and it's just over 7 pages long, but the first 2 pages are nothing but Dim's and Request.Form's. I'm going to need these same dims and request.forms on each of the pages that I break off of the main one, so I was considering just putting them all into a seperate file all to themselves and then using #include file. My question is, what kind of impact do includes have on load time. Do they slow page loading any, and if so is it a noticable slowdown? -jeremy -- For unsubscribe and other options, including the Tip Harvester and archive of thelist go to: http://lists.evolt.org Workers of the Web, evolt !