A typical solution for me is to create a session structure to hold all form values. I then split my forms into different tabs or accordion layouts. When the user finally submits the form you can just duplicate the form values into session, do validation and return to the form if need be.
Dan On Jan 11, 2008 11:15 AM, Mike Haggerty <[EMAIL PROTECTED]> wrote: > I just wanted to get some ideas for doing a multiple screen form. > > Here's the situation. I have alot of data to collect. It's all going > into the same database table. I have a number of different forms that > will collect this information. Of course the old school way would be to > pass hidden inputs around from one form to the next. I'm trying to > avoid that. How do most folks do this? > > My thought it to create a record object on the session scope when > entering the first form, saving the first form's data into that record > object when beginning the second form, etc....and then saving that > record after the last form's post. > > Is this the 'best practice'? > > Thanks! > Mike > > -- > Michael Haggerty > Internet Applications Developer > SiteVision, Inc. > <e>[EMAIL PROTECTED]</e> > <p>540.343.8322 x116</p> > > > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- > Reactor for ColdFusion Mailing List > [EMAIL PROTECTED] > Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- > > -- Thank You Dan Vega [EMAIL PROTECTED] http://www.danvega.org -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
