Hi,
Kind of stuck between a rock and a hard place on this.
I have 3 pages - all of which ask for user input through various text/radio/picklist controls. On post back, these entries are to be written to the relevant fields in the new row of a table.
I was thinking of storing a datarow/datatable with one row in the session object so that each postback simply replaced the referenced datarow item with its value.
Obviously no connection will be made back to the underlying database until the third page is validated and submitted.
Thus, would anybody like to argue for/against this method? Goes without saying it is down to the number of active sessions, but essentially, is a datarow object too "heavy" to be stored in the session object?
Cheers.
Glyn.
Kind of stuck between a rock and a hard place on this.
I have 3 pages - all of which ask for user input through various text/radio/picklist controls. On post back, these entries are to be written to the relevant fields in the new row of a table.
I was thinking of storing a datarow/datatable with one row in the session object so that each postback simply replaced the referenced datarow item with its value.
Obviously no connection will be made back to the underlying database until the third page is validated and submitted.
Thus, would anybody like to argue for/against this method? Goes without saying it is down to the number of active sessions, but essentially, is a datarow object too "heavy" to be stored in the session object?
Cheers.
Glyn.