Messages
Reply
Edit
Delete02:13 pm
3SE0UI971
| From: | Rick Strahl |
| To: | John Prescott |
It's an extremely bad practice to not allow the back button because it's an integral part of the browser. If you disable it you basically go against one of the core features of the browser. The trick is to program defensively in such a way that back button operation doesn't screw up your code. The most common problem is reposting data that was already submitted (ie. add a new record, then post again to submit again - easy fix: your code should check if the data already exists then update it instead).
The article ref'd by Bob also points to using the cache headers to avoid reposting of POST data - you can do that Response.AddForceReload() in Web Connection. But again that's effectively 'disabling' the feature too and I would consider even that bad practice. The real use case for a 'go back' and resubmit is effectively an 'update' operation. If you build your forms correctly (with business objects especially) doing updates or new entries can be nearly transparent providing the functionality that most users would expect.
+++ Rick ---
Is it popssible to disable a back button in IE from within Web Connect?
If not can it be disabled in HTML coding?
West Wind Technologies
Making waves on the Web