Webform model and its shortcomings?

[Weston Weems]

Hello, first of all I'd like to state that I dont mean to
point out asp.net as being bad. So far I've very much
liked the concept of webforms. I just seek advice to
making user experience more pleasant for end user.

Dillema at hand...

I've got a multiple part "wizard" like interface that
works rather well. Collects the users data and and once
the submit button is hit on the last page, data gets
verified one last time, then inserted into the database.

My problem lies in the fact that I cant trust users to use
only the supplied navigation links etc... I've seen more
complains than one would care to know about... saying they
hit back or refresh and got page expired warnings.

So my question to you experienced developers is, how can I
avoid such things? I am not 100% sure I know what I did
that requires the page to time out, let alone how to avoid
it in the future.

Thank you in advance for the advice, and if you can,
please cc a copy to:
wweems@SPAM_SUCKSgmail.com, without the spam_sucks part =)

Thank you very much.

 

[John Saunders]

Hello, first of all I'd like to state that I dont mean to
point out asp.net as being bad. So far I've very much
liked the concept of webforms. I just seek advice to
making user experience more pleasant for end user.

Dillema at hand...

I've got a multiple part "wizard" like interface that
works rather well. Collects the users data and and once
the submit button is hit on the last page, data gets
verified one last time, then inserted into the database.

My problem lies in the fact that I cant trust users to use
only the supplied navigation links etc... I've seen more
complains than one would care to know about... saying they
hit back or refresh and got page expired warnings.

So, what does your problem have to do with webforms and their shortcomings?
The exact same problem occurs for HTML pages.

John Saunders