Unless you timeout the page immediately, they are going to read it from
cache, which means no trip to the server. If you time it out immediately
after Response, however, the use will either refresh the page or get a page
timed out page.
For ASP.NET:
I believe you have a potential architecture problem. There are some
instances where Server.Transfer is in order, of course, but in more cases
than not, it is a sign that some code needs to be moved out of pages and into
classes. This facilitates the model of a form being used to completely
perform a task, rather than having to pass the request to another page.
For traditional ASP:
ASP is a sticky wicket, as it forces you into a model where you use pages
like classes. You can overcome this with VB COM components, but that is an
additional skill developers will have to have to code in your shop. You can
also, somewhat, overcome it with include files.
---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Stuart" wrote:
Hi There
Is there any event that can automatically fire when a users Browses back to
an .asp Form ?
For example - if I have a datagrid that uses a SELECT button to redirect the
user to another page (using server.transfer) if they then look at the
information on the new page and click BACK in their browser so they go back
to the original page with the datagrid - what can I use to identify this has
occurred to the server and trigger some code ??
Thanks for your help
Stuart