1) each page dumps in the database, and you get it all out at the end, this allows back and forth between pages. 2) if the form will fit, store it all in a cookie, get the pengoworks form field api thingy for that . 3) do a WDDX conversion of each form on submission and send it to the next page and store it in a hidden form field. This way you still get all your original fieldnames at the end.
Russ > -----Original Message----- > From: Damian Watson [mailto:[EMAIL PROTECTED] > Sent: 10 September 2004 18:52 > To: [EMAIL PROTECTED] > Subject: Re: [ cf-dev ] Multiple page questionnaires > > Exactly, the whole fed up thing is what I'm worried about... > can always get it to email them if they got bored and went > away if it's stored in a table > > > [EMAIL PROTECTED] wrote: > > >yep, that's a definite issue if an individual form is long enough. > >i.e. it takes longer to fill out that form and submit it than your > >session timeout is set at. > > > >although if you're splitting it across many pages, hopefully it > >wouldn't take that long to fill out any one page. unless > they get fed > >up with it and go for their lunch break or something > > > > > > > > > > > > > Damian Watson > > > <[EMAIL PROTECTED] To: > [EMAIL PROTECTED] > > ign.co.uk> cc: > > > Subject: > Re: [ cf-dev ] Multiple page questionnaires > > 10/09/2004 18:19 > > > Please respond to dev > > > > > > > > > > > > > > >Thanks Duncan, that's given me some ideas ;) Going to have to be the > >2nd of the three I think- it's a very long questionnaire so I guess > >using session structs may lose some users after timeout > > > >[EMAIL PROTECTED] wrote: > > > > > > > >>1. pass the information between pages with hidden form fields. this > >> > >> > >method > > > > > >>is probably fine, although if your form has quite a few pages and > >>fields, you'll end up with lots of hidden fields. if you > also go back > >>to the previous page if there's an error in the form (e.g. they've > >>left a field blank), you'll have to pass all this > information back too. > >> > >>2. store the form information in a table. either this could be a > >>temporary store, which then gets deleted after form completion or > >>periodically, or it could be the actual table the form results are > >>meant > >> > >> > >to > > > > > >>end up in. if your form is created dynamically, you'll > need to have a > >>table flexible enough to allow for various types of answers > >>(text/numeric/longtext/boolean etc). probably the most potentially > >>difficult way of doing it IMHO. > >> > >>3. store the information in a structure in the session. > probably the > >>simplest way to do it. then at the end of the form, just transfer > >>this structure to an email/database/whatever. > >> > >> > >> > >> > >> > >> > >> > > > > > > > >> Damian Watson > >> > >> > > > > > > > >> <[EMAIL PROTECTED] To: > >> > >> > >[EMAIL PROTECTED] > > > > > >> ign.co.uk> cc: > >> > >> > > > > > > > >> Subject: > [ cf-dev ] > >> > >> > >Multiple page questionnaires > > > > > >> 10/09/2004 12:45 > >> > >> > > > > > > > >> Please respond to dev > >> > >> > > > > > > > > > > > > > > > > > > > >> > >>Hi, > >> > >>Anyone got good pointers/ tips/ resources for creating > multiple page > >>forms i.e. a registration process with several stages... ?? What to > >>look out for, pitfalls etc etc > >> > >>d > >> > >>-- > >>These lists are syncronised with the CFDeveloper forum at > >>http://forum.cfdeveloper.co.uk/ > >>Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > >> > >>CFDeveloper Sponsors and contributors:- *Hosting and > support provided > >>by CFMXhosting.co.uk* :: *ActivePDF provided by activepdf.com* > >> *Forums provided by fusetalk.com* :: *ProWorkFlow provided by > >>proworkflow.com* > >> *Tutorials provided by helmguru.com* :: *Lists hosted by > >>gradwell.com* > >> > >>To unsubscribe, e-mail: [EMAIL PROTECTED] > >> > >> > >> > >> > >> > >> > >> > >> > >> > >> > > > > > >-- > >These lists are syncronised with the CFDeveloper forum at > >http://forum.cfdeveloper.co.uk/ > >Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > > >CFDeveloper Sponsors and contributors:- *Hosting and support > provided > >by CFMXhosting.co.uk* :: *ActivePDF provided by activepdf.com* > > *Forums provided by fusetalk.com* :: *ProWorkFlow provided by > >proworkflow.com* > > *Tutorials provided by helmguru.com* :: *Lists hosted by > >gradwell.com* > > > >To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > -- > These lists are syncronised with the CFDeveloper forum at > http://forum.cfdeveloper.co.uk/ > Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ > > CFDeveloper Sponsors and contributors:- > *Hosting and support provided by CFMXhosting.co.uk* :: > *ActivePDF provided by activepdf.com* > *Forums provided by fusetalk.com* :: *ProWorkFlow > provided by proworkflow.com* > *Tutorials provided by helmguru.com* :: *Lists > hosted by gradwell.com* > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > -- These lists are syncronised with the CFDeveloper forum at http://forum.cfdeveloper.co.uk/ Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ CFDeveloper Sponsors and contributors:- *Hosting and support provided by CFMXhosting.co.uk* :: *ActivePDF provided by activepdf.com* *Forums provided by fusetalk.com* :: *ProWorkFlow provided by proworkflow.com* *Tutorials provided by helmguru.com* :: *Lists hosted by gradwell.com* To unsubscribe, e-mail: [EMAIL PROTECTED]
