Thanks for reading. I have an ASP handle page that creates a session containing the UserID. Basically, the login page creates the session for the username and redirects to the handle page. The handle page calls a recordset and filters by the user name from the login page, therefore getting the UserID. I try to set a session with the UserID and Response.Redirect to the appropriate page, but the session does not set. If I reload the handle page a second time, the session will set and redirect just fine. If I remove the response.redirect from the page and just try to write the session value, it works on the first time. I guess my question is why does the response.redirect some how kill or not pass the session on the first try? It is the last thing on the page and called after the session is set. Any ideas?
hmm, I have been using something similiar, but not run into "missing sessions". Silly question, but have you checked to make sure all your spelling is matched between the instantiation of the session, and the attempted read of the session?
Not a silly question at all..... it happens all the time. Ive checked and rechecked, nothing. I checked where the session is created vs. where it is called, all is the same. If I try to write the session value instead of redirect the page, it will write it properly on the first try. Its strange, never seen anything like this before.