First, thanks for looking at this it is appreciated.
Here is what I have and what I would like see happen.
I have two ASP pages, page one the user selects criteria via a form. Upon clicking submit they are directed to page two where we search the db using their criteria with the results, if any, displayed on page two.
If no matches are found we return them to page one where we display the appropriate message based on a querystring that we attach to our redirection. Example: Server.Execute("models_searchengine.asp?Action=NoMatch")
Everything works as planned except when the user gets a match after they previously didn’t have a match on page two. If they click the back button on either their mouse or browser it returns them back to page one with the above url, which in turn displays our nomatch error when in reality they have a match.
What I like to do is clear that buffer or cache that is storing the previous url when there is a match on page two, OR better yet every time I hit page two clear it at the very top of the page. Then if there is a problem return them to page one with the correct querystring. Is this possible? If so how do I remove that stored url when they hit page two?
Another solution would be a different way to handle the return to page one and how I display the error message. Anyone have a suggestion?
Bottom line I need to clear the Querystring Error so if they use the back button no message appears when they have a match.
Thanks Again
Life's a journey enjoy the ride...
jazzz
Here is what I have and what I would like see happen.
I have two ASP pages, page one the user selects criteria via a form. Upon clicking submit they are directed to page two where we search the db using their criteria with the results, if any, displayed on page two.
If no matches are found we return them to page one where we display the appropriate message based on a querystring that we attach to our redirection. Example: Server.Execute("models_searchengine.asp?Action=NoMatch")
Everything works as planned except when the user gets a match after they previously didn’t have a match on page two. If they click the back button on either their mouse or browser it returns them back to page one with the above url, which in turn displays our nomatch error when in reality they have a match.
What I like to do is clear that buffer or cache that is storing the previous url when there is a match on page two, OR better yet every time I hit page two clear it at the very top of the page. Then if there is a problem return them to page one with the correct querystring. Is this possible? If so how do I remove that stored url when they hit page two?
Another solution would be a different way to handle the return to page one and how I display the error message. Anyone have a suggestion?
Bottom line I need to clear the Querystring Error so if they use the back button no message appears when they have a match.
Thanks Again
Life's a journey enjoy the ride...
jazzz