>The nice thing about this is that you've got a record of the "raw" data the user filled in, and it's really easy to repopulate any pages of the web form (esp. if you've got a databinding class like the one Rick showed in the current issue of CoDe, or MM.NET). You can also do data analysis after the fact to see where people might be bailing out of the process (is the form too complicated? Are we asking for info. they don't have handy?).


Yeah, this is pretty much what I do too. Actually, for Wizard type interfaces I use a 'navigation' object that holds any state variables that I need for the succession of Wizard pages. If I need to this object is persisted to a Session object... saving to DB works too of course but for transitional data like Wizard options and settings saved which is pretty light usually I just use an object to which I then bind with the databinding stuff...

FWIW, if you're using this databinding stuff from me you'll want to use the stuff from the Web Store since that's much more sophisticated than the stuff from the article...

+++ Rick ---