Global.asa Question: Views wanted

[PatHastings]

Hi,<br>I'm writing a data entry process that has a number of forms. The data entered on each form is connected via an ID key which is held in the database but passed from form to form via a session variable. <br><br>As such there is a heavy reliance on the user completing all of the forms without the session timing out. Normally this won't be a problem. <br><br>My concern here is what happens when the session does time out half way through the series of forms. I have put a check at the start of each ASP to make sure the session is active. What i am wondering is: Is there anyreason why I shouldn't put some code in the session_onend event of the global.ASA so that if the session ends halfway through an update then it will run a stored procedure on the database to delete all partial information entered.<br><br>Anyone have any views on the matter?

 

[palbano]

Dear Pat,<br><br>My preference is to use hidden form variables rather than session variables for the type of form to form persistence that you are describing. When more than two forms exist I would encapsulate the read/write routines into a single file that is included in each page where needed.<br><br>&quot;But, that's just my opinion... I could be wrong&quot;.<br>-pete

 

[PatHastings]

Pete,<br><br>YOu're right that is a better way. Cheers for the tip<br><br>Pat