Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Collecting ASP.Net form data in session objects?

0 views
Skip to first unread message

tmn

unread,
Jan 6, 2003, 11:54:34 PM1/6/03
to
I'm new to ASP.Net development, so forgive me if this is a
dumb question. I need to build a multi-page data
collection form (its a mortgage pre-qualification form -
very long and detailed) using ASP.Net but with no back-end
database of any sort. I need to collect all the user's
input across 2-4 pages of form data and package it into an
e-mail. The idea I'm starting with is to append each
page's data to an XML file stored in a session object (no
client-side code allowed) and on the last page, pass the
XML into another processing page that will package the
data into an e-mail. The e-mail info is then routed
internally where someone will MANUALLY data enter the
contents into a customer management system - I'll at least
use XSL to render the XML in a user-friendly format.

My concerns are:
1) Memory management - the more users, the more XML in
session objects = more memory requirements
2) Maintaining the data while the forms are in process -
I'll need to write a lot of code to handle situations
where users go 'back' a page and edit their previous
answers
3) Some of the forms need to be dynamically generated
based on previous answers - if the user goes 'back' and
changes a key response it will change the pages down the
chain, potentially invalidating some of the info stored in
memory.

Is this plan sound or is there a better way to handle
multi-page form data collection? I'd prefer to use a
database to capture each page's info along the way and
treat each page individually from a data collection/edit
process but we can't spend the $$$ on a database, not even
MySQL!

Steve C. Orr, MCSD

unread,
Jan 7, 2003, 2:12:29 AM1/7/03
to
I suggest you consider using a strongly typed dataset for this.
Basically you'd have an in memory database customized for your data that can be easily serialized to XML and back again.  (we're talking 1 line of code)
You can store it in session state or send it in an email or whatever you want.
Here's more info:
 
Another approach would be making it all one ASPX, with each of your "pages" on a different panel in that ASPX.  Then you just show the current panel and set the visible property to false for the others.  This technique isn't especially scalable, but it has the advantage of being nice and simple, with all of your values easily available at all times.

--
I hope this helps,
Steve C. Orr, MCSD
http://Steve.Orr.net
 
 
0 new messages