detox — Wed, 13 Feb 2002 14:07:07 +0000

if you arent using session variables at all (they are sometimes a necerssary evil) the simply use :

<?php
<%@ ENABLESESSIONSTATE=False 
?>

here is a link about the pros and cons of using session variables

4guysfromrolla.com/webtech/092098-2.shtml

Peter J. Boettcher — Tue, 12 Feb 2002 14:13:37 +0000

If you want to make sure the page doesn't get cached try including the following at the top of your page:

Response.AddHeader "cache-control", "private"
Response.Addheader "pragma", "no-cache"
Response.Expires = 0

Be sure to delete your cache first

ROB — Tue, 12 Feb 2002 00:36:53 +0000

that's not the problem, the exact same error with the exact same line of code (including the semicolon) is displayed, even if the file no longer exists on the server.

i figured out a fix though. if file1.asp includes file2.asp, and you want to change something in file2.asp (such as fix an error) you need to re-upload both file1 and file2 for changes in file2 to be visible. after reading a bit more about ASP i think it may have to do with the session, once the included file is in memory ASP doesn't think it needs to read it again, but it should at least check to see if it's been modified...

Peter J. Boettcher — Mon, 11 Feb 2002 22:38:34 +0000

Try removing the () like:

response.write "blah blah blah"