I guess I understood Shiloh to mean that he didn't want to perform inter-tab/page queries to reload the data from the previous/next tab. I still believe that using the multipart tabbed form, there is no need to "save" anything when switching from tab to tab because the form never reloads during a given session, this is all client-side action just hiding layers/divs to expose the next form tab. Once all pages have been entered or modified to the users satisfaction, then that form is submitted in it's entirety to the DB. If you need to see it again later, just load it up and do what you need to do until you update that record again. I guess Shiloh needs to input here to clarify his needs and intentions. Shiloh? > -----Original Message----- > From: Luke Skywalker [mailto:masterskywalker@tpg.com.au] > Sent: Tuesday, September 16, 2003 10:14 PM > To: DLAKODUK@mn.rr.com; php-db@lists.php.net > Subject: Re: Saving state > > > Yeah, that is a good way to do it, i would do something > similar too but > Shiloh > seemed to not want to requery the database, althought querys > in this case > would > be the quickest and simplest way to get the historical > information, which > would be > stored in the database already, and as you said, update > querys if you want > to change > the information loaded into the form. If you need to avoid > the database, the > only > other way i can see of keeping the information is adding it > to variables at > the same > time as you add it into the database, and when you need to > re-access the > info, pull > it from the variable instead of the database, but that could get messy > > Luke > > -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
