I developed this form, and it's very large. The client tells me it could take up to two hours for someone to complete the form, which means I'm going to run into the session timing out, and the users loosing their data.
Is there a smart/easy way to work around this, aside from increasing the timeout on the server?
use a db.
store all data in a db (maybe a table with a column for each sessionvariable that you use ?) and then sent the primary key value of this table inside each for as a hidden field --> make sure to encode the PK value so that users can't manipulate them.
This way you can then select the data from that table using the decoded PK value inside your where-clause
05-28-2004, 05:18 PM
Assuming the users are required to login to fill out this form then you could provide a save button on each page to save their current data to a database as Raf suggested and each time they go to a new page of the form save the data from that page to the database automatically as well.
I would hope that you provide a login for this as you could then implement a feature in conjucntion with the save button for them to come back later to finish filling out the form.
another option would be to use persistent cookies ...
you could encode the data using the password as salt. then after login, store the pwd in a sessionvariable (i know, not 100% OK) and then if this sessionvariable is set on each pagerequest + use it to decode the values.