I have an access databse that has to be webenabled (working for the government I can't just do it with access because not everyone has the same version so I have to start from scratch using ASP, JavaScript, HTML, and eventualy incorperate XML. The people I am creating this are very resistant to change, so the more like the original the better. The original had 6 "tabs" to navagate each section of the databse. The tables were setup by an extreme amature (table names were named stuff like "tbl_julythegreat" july being the name of the programmer, just to give you an Idea.) Rather that redo the whole thing with new naming conventions and create a bigger nitemare what I am going to try to do is this. Vice saving the information as they go (because they may not enter the correct information and as the database in access stands now there is no error checking) I am taking all of the 77 possble values and putting them in a hidden form. That way they can jump from page to page and keep all of the values. Once the visable form is filled out they have to save it manualy, like any other windows application. I think I have found an onBeforeUnload that will check to see if it has been saved before they try to leave. so this function would save the visable info into the hidden form, and then submit the hidden values to the page they want to go to. example:
the user starts on the personal information page. they fill it out, then click the "work info" button. The function copies the form values to the hidden form. Then changes the action to "workinfo.asp". inside workinfo.asp the hidden form is populated again with the current hidden values (to be submitted to the next page they want to go to)
they fill out that page, the function copies the values from the form to the hidden form then changes the action to what ever page they then want to go to. by the time they get to the 3rd page they have the values from "personal info, and "work info" tucked away in a hidden form waiting to be submitted to the 4th page or saved to the database.
Now i'm sure you're confused because I sure as heck am.
ultimatly I am trying to avoid using asp session variables to eliminate some problems and keep from using server memory to save 77 session state veriables (and using an array would just get confusing trying to keep them in order).