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]
