Im new to the programming world aside from HTML so be gentle with me! This project is actually Asp.net w/ C# but its general knowledge so hopefully someone can help. I've managed to make a form post the field data into an SQL database and it posts back to the current page with a confirmation or error message (also with range validations). I want to add another step/page that would allow me to see the values Im about to submit before actually doing it like a "are you sure this is what you want to submit" page.

Should the form store the field data into variables to be displayed on this verification page and then sent those to the DB? Or should the form go ahead and post it to the SQL table and if they choose to change it, remove the data from the table and direct them back to fix the problem? Like I said, Im still new to C logic so any recommendations would be very helpful since Im at a crossroads here. Thanks in advance!

~Dan

store the values as variables in session, cookies or a temporary table, the have the user verify and commit the transaction.

Take advantage of the .Net postback model.

Fill in the form, when the user posts back, show a panel with some literals containing thier data, if they click 'save' in that panel, save it to a database

sean

I originally had this setup as a Postback BUT they wanted to add some confirmation pages in the middle so that didnt work. I actually got it worked out finally but I stored the initial values as a session var and then on the next page it verifies the info and they can go back to fix it or submit it, where it forwards them to a nice pretty thank you page. So it works I guess.

You could use the postback model and one page that acts differently depending on what 'mode' it's in. Something like:

if(!PostBack) {
...
}

You can still use the postback model you know, just use some panels which get shown / hidden on a buttons click event...

but if your solution works don't bother trying to change it!