This usually happens because you have Response.Redirect commands or meta
refresh tags in a page. When a visitor gets redirected by one of these and
then clicks Back, they encounter the redirection again, and get sent forward.
For meta refresh tags, you can minimize this by specifying a non-zero wait
time for example:
<meta http-equiv="refresh" content="2; url=forward.htm">
give the visitor 2 seconds to click the Back button a second time.
For Response.Redirect commands, yot generally have to add some program logic
that decides where the visitor came from and where they should go. Howver,
this varies depending on the situation.
Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------