Classic ASP Discussion - How to split an input form

Print Page | Close Window

How to split an input form

Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: Classic ASP Discussion
Forum Description: Discussion on Active Server Pages (Classic ASP).
URL: https://forums.webwiz.net/forum_posts.asp?TID=7361
Printed Date: 01 April 2026 at 2:32am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com

Topic: How to split an input form

Posted By: stevem2003
Subject: How to split an input form
Date Posted: 18 November 2003 at 8:11am

Hi
I have been trying to find out how to do this for some time, but I don't really know what I should be looked for.
I have a really long input form, to enter info into a database, can this be "split" so that I can have nicely grouped input fields and combo boxes, so the user presses Next to move to the next page? And then the whole record is saved on the last page.
i.e. like a booking form.

Any suggestions, tutorials, websites would be appreciated

TIA
Steve

-------------
There's no point running if you're on the wrong road!

Replies:

Posted By: michael
Date Posted: 18 November 2003 at 4:54pm

You need to save the values from the previous form in either a session object or a cookie. So once you are ready to post it to the db, retrieve the cookie/sessions

-------------
http://baumannphoto.com" rel="nofollow - Blog | http://mpgtracker.com" rel="nofollow - MPG Tracker

Posted By: zMaestro
Date Posted: 19 November 2003 at 3:12am

I pass the data between pages through the forms, making the values of Form1 (page1) hidden fields in Form 2 (page2).

may be session or cookies are better, but I am not familiar with :$.

e.g (form 2 page 2)

<Input type="hidden" value="<%=Request.Form("field1")%>" name="field1">

Posted By: stevem2003
Date Posted: 19 November 2003 at 3:22am

Many thanks zMaestro & michael,

just need to decide which way to go

-------------
There's no point running if you're on the wrong road!

Posted By: MorningZ
Date Posted: 19 November 2003 at 10:16am

i would think the best way to do it is to have the first page of fields do the INSERT, grab the new ID, then pass that along in the querystring, hidden form field, session....

each subsequent page, do an "update" on that record.....

on the last page (and last update), set some column like "Is Complete" to true so that you (easily) know in the database that a record is complete or not

if you don't save until the very end, imagine your web page visitor's frustration of filling out multiple pages only to time out or have their browser close and loose all that time and effort because none of the data leading up to the last page was saved to the DB yet

-------------
Contribute to the working anarchy we fondly call the Internet