There are a couple of useful posts in either the 'beginning' or this 'professional' area of this forum. If you cant find then narrow your search down ny looking for contributions fro 'Imar' Im sure he was involved in what i remember to be a lengthy very wise bit of information on this.
In short and IME state management is an issue in the classic ASP world because Session_OnEnd doesn't fire when you think is would and most people think its supposed to. If you find this post im talking about it explains why in detail from memory. My advice is that this topic is in the 'to hard basket' in our world (this issue has been solve n the .NET world of course) Try not to use session variables in your application. Carry values from page to page using the request.form or request.queryString - There should never be a need to carry values around using session("someName")! If you dont get this concept and think you cant carry values from page to page becasue you dont have a form on every page then put a form on every page. A form can have all hidden form variables dont forget.......Anyhow I wont bang on, im sure you will find the post im talking about. I even remember some very clever input that suggested a solution that works 'most of the time' but it was an awful lot of effort from memory....
Of course you can increase the timeout. Place a global.asa file at your applications root and include something like:
Session.Timeout = 40
Server.ScriptTimeout = 50
Wind is your friend
Last edited by mat41; July 12th, 2012 at 06:53 PM..
Reason: addional info