Dan's covered pretty much everything. The only thing I might add is that
what method you use really depends on the type of application. It certainly
is less work for the database and server, and probably neater programming,
if you simply pass the form fields between pages and do your validation
between pages. However if a user expects to be able to return without
finishing the form process and not have to fill in any data you have a
choice between using cookies, and saving the data in the database, and that
choice comes down to whether you want to create a routine to rid your
database of incomplete data that is left around from unfinished forms.
So it really depends on the application and some thought into the possible
processes your users may go through in filling the data out. I have used
any combination of different methods for job resume systems, course
applications, surveys, etc.
Garth
At 07:03 27/07/02 -0400, you wrote:
>John I have done this very thing with a pop up small window that breaks the
>form into many pieces and gives them a choice at each one to close window or
>pick the next part. This was for a medical office application where they
>might not want to get all the patient info on a new patient with the first
>phone call.
>
>In that case I do an insert with each form part of the large form is broken
>up in the pop up window and then use JavaScript to close the window with the
>last submit button. Just remember to pass the args from each part as hidden
>inputs with each time.
>
>I also suggest you check for missing or malformed info on each part so they
>can use a back link to fix it.
>
>
>--
>Dan Stein
>Digital Software Solutions
>799 Evergreen Circle
>Telford PA 18969
>Land: 215-799-0192
>Mobile: 610-256-2843
>Fax 413-410-9682
>FMP, WiTango, EDI,SQL 2000
>[EMAIL PROTECTED]
>www.dss-db.com
>
>
> > From: "John Hollister" <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > Date: Fri, 26 Jul 2002 11:37:48 -0700
> > To: Multiple recipients of list witango-talk <[EMAIL PROTECTED]>
> > Subject: Witango-Talk: large forms
> >
> > 1. Should be simple I hope just want input on what other have done, to
> > better help me on this quest
> > Have a large form, there is 1 part for inquiring information /basic
> > stuff needed on the first form and can not break them up.
> >
> > The rest can be broken down , into group of info I guess just not sure
> > which way to go. I can feed them one large form, but though I might be
> > feeding them too mauch at one time. But don't have a problem with that.
> >
> > Anyinsight would be helpful for me to take action.
> >
> > 2. posting a form to a pop has any one done this. I don't want to leave
> > a form trail for their back button to feed back to the submition action.
> >
> >
> >
> >
> > System IE 5 or great only, but any input will be helpful
> >
> > thanks
> >
> >
> > ________________________________________________________________________
> > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> > with unsubscribe witango-talk in the message body
> >
>
>________________________________________________________________________
>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
