I've seen long registration forms broken up into two pages. How can I have one page submit info to a table, and then another page submit more info in the same table?
Well, can you not write to the db from both pages then?
Is the second page gong to replace/update things from the first page?
The more details you can share now, the easier it is for us to help.
The second page doesn't replace anything in the db. It only replaces the nulls that automatically fill in after the first page gets submitted. I just dont know how to insert the second page of data to the same user's row. If thats unclear let me know.
Then again, actually see what you have for a form code would make it a whole lot easier to understand.
Last edited by OctoberWind; 02-18-2009 at 08:34 AM.
Reason: quotaions: yea, you dont have to open/close so many singles/doubles, but still... it works...
Or you could create one big form, which you split into several hidden divs, which you then use dhtml to hide or show.
While the initial page will take a little longer to load, overall, the solution will be much faster (and therefore nicer to use) because it's not using bandwidth to pass, and then re-pass variable values from one form to the next. When the user clicks on [Next], the next page of the form will appear instantly, and your user can switch seamlessly between pages of your form without you having to worry about any coding at all.
The two downsides to this are a)dealing with browsers that don't have javascript, and b)dealing with branched forms (that is, forms that change for the next page according to some value set in the last).
CTB
Oh Lord, please help me be the person my dog thinks I am.
Update function is perfect! one question. You mentioned earlier that i could pass the values. I can pass the values just fine but once the second page is filled out how do i submit all the values? Would this be right:
Bookmarks