Persisting form data across page load

[John Hoge]

A common problem in database updates in the maintenece of "domain
tables". For example, a product database has an option for color. When
entering the specifications for a new product, a domain table is used
to populate a drop down list of available colors.

Simple so far. But what if the user wants to create a new color
specification on the fly? Let's say that this is a complicated process
requiring it's own page with validation code. Once the process is
complete, the user needs to be redirected back to the half completed
form so he can finish.

What is the best way to persist all of the data that the customer has
entered before? One option is to place the results of each control
into a session variable, and then write code to put it all back into
place, but that's kind of sloppy, and I could have done that in
classic ASP.

Is there some magic .net solution to persisting a form across page
loads?

 

[Jeffrey Palermo [MCP]]

John,
No, there is not a "magic" .Net solution for this. You need to save
temporary information, and Session is one of the options to do this.
Actually, since you need information on two different pages, session is
probably the best option.

Best regards,
Jeffrey Palermo

 

[Guest]

Hi,
You can open the second form as dialog box using client-side java script.
You will not lose your session when you close the dialog.
Krishna Jammula