Collection of data in multiple forms

[anonymous]

Hello,
I need to collect a lot of data before really committing changes

For examples
I need to collect User Personal Information
Then Collect CreditCard information
etc.

Today I have it in one page
Which is too much in my view

I would like to break it down in to two or more pages and process it at the
end

I was thinking of collecting the data and storing it in a Session object and
then process all of it in the last page

Are there any issues in storing the data in Session variables

Any other ways I could do it

Thanksin Advance

 

[Cowboy \(Gregory A. Beamer\)]

Use a multi-panel form (allows you to "wizard" the page). Show each panel in
order and keep the info stored in the controls on the page. Even when
invisible, you will still hold the control's info in ViewState. This way you
do not have to work with session elements.

If you need to go to session, create objects that have the info you need to
persist to the database when the user is finished and keep the objects in
session. Be sure to clear them out after you are done with the order.

--
Gregory A. Beamer

*************************************************
Think Outside the Box!
*************************************************

 

[Richard Carpenter]

That's great information, Gregory. I've just begun working on my first
legitimate ASP.Net web site, and I am also working on implementing a
data entry screen with hidden panels to accommodate a large amount of
data. My problem is that the additional panels will be used to display
(or hide) individual grids containing child data. Is there a way of
adding multiple child rows without actually writing them to the
database, pending the user ultimately clicking the Save button on the
parent data section?

I'd like to design it so that when the user clicks Save on a child data
panel, it doesn't actually save it to the database, only to the local
datatable, with all changes for both parent and child tables written to
the database at the same time when the user clicks the main Save button
- or something to that effect. Hmm, I'm guessing that a scenario like
that would also require me to trigger the writing of the data in the
correct order to avoid RI conflicts.

Rich