p2p.wrox.com Forums

Need to download code?

View our list of code downloads.


  Return to Index  

proasp_codeclinic thread: 1 page vs. many pages and transition


Message #1 by dont worry <aspmailbox@y...> on Mon, 25 Mar 2002 09:07:43 -0800 (PST)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "dont worry" <aspmailbox@y...>
Subject: [proasp_codeclinic] 1 page vs. many pages and transition


: It seems easier to build a portion of my app in 1 asp
: page even though it 'looks' like many pages to the
: user.  I noticed the size gets bigger so I ship pieces
: to an include file which reduces size.
:
: Is it better to cut it up into smaller pages and if so
: what is a good way to make the transition of info.
: from one to the other?  I've tried response.redirect
: with querystring values, but querystring is limited.
:
: I build a form and post back to the same page to check
: info.  Is there a way to check the info. and POST the
: info. to the next page if it is good? I don't want to
: have a page that says so far so good to continue click
: here.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Have you tried to use server.execute("Another_page.asp")or server.transfer
("Another_page.asp")?
it might do the trick if you are using ASP 3.0.

regards

If the information from each page is being server-side validated, then
persist it somewhere (eg to database), and generate a key for the user. 
Pass
this key in the Querystring.

Alternatively, if the data *isn't* being validated until right at the very
end (ie when the user submits the last page), then I'd handle it like this:

a) do client-side validation on each page. This is just to warn the user if
they have made a mistake, or missed something out.
b) pass all the data from page to page using a cookie, or hidden form
variables
c) after the user has submitted the last page, validate all the data
serverside and put it into the database if it is OK.

Cheers
Ken


  Return to Index