Hi,

I have an ASP page, and I have been using Response.redirect with no problems. So far.

Of course this means more up/down transfers to move around pages, and a friend suggested that I look into other methods.

So I looked in my book and found Server.Transfer. Looked like it does what I needed.

So being me, I slapped it in over the Response.redirects..




As you can guess it failed miserably, erroring on the opening of a recordset from an Access mdb which it had no problem opening before.

** None of the code to open the connection/recordset has changed. **

So I reupdated the code back to response.redirect, however whatever it did it stuffed up the page. Again it errored on the opening of the recordset, but weirdly it only errored on a refresh or second attempt to open. IE.. open first time, worked fine. Refresh or recall the page, and it errores 500 server error.

I was wondering what the hell happened?
Was it like Access, and just 'corrupted' somehow?

I'd like to know incase it happens again in the future.

I ended up downloading the original file from the web server and re updating sections, and it works .. currently.


Vince