The results of this could be beneficial to any WEB developer.

I am using the most recent version of Mere Mortals along with Infragistics NetAdvantage 2004 Vol2. I am wondering what the best way is to persist the value of objects from a Parent page to a child page and then back.

Parent <--->> Child

Assume you are editing, not adding, a record on the Parent page. Assume the Parent (table) page has >250 (fields) individual textboxs, dropdownlists, radio buttons, check boxs, etc. In other words, too many objects to want to save the values individually.

I know you would say, why have 250 fields on a Web Page. With Infragistics WebTab an unlimited number of fields can be displayed within a reasonable amount of space. So please entertain this question.

There is also a button on the page which will allow you to Add a record to a mmDataGrid object (child table). When you press the Add button the Child page is called. 'Response.Redirect("Child?ParentID="+ParentID)' You select the record to save back to the Parent page and are automatically redirected back to the Parent page. 'Response.Redirect("Parent?ParentID="+ParentID)'

This loads the parents session datasets and resets all the values back to their original state because the >250 fields were not persisted back to the dataset and/or the record was not saved prior to adding the Child record.

What is the best way to persist the object values and how to do it? What are the advantages and disadvantages of each, particular to server memory and performance. Assume >100 concurrent users.

1. Session["objectID"] <--- I know how to do this
2. Cookies
3. Form Post
4. ViewState
5. Context

I currently use cache to persist static tables (dropdownlists) and Session[] to persist dynamic data entry tables.

Thank you,