Abandon Session

[rn5a]

In a MS-Access database application, the following code resides within
the *Catch* block of a *Try....Catch* block:

=========================================
Try
'some code
Catch ex As OleDbException
If (ex.ErrorCode = -2147467259) Then
Response.Write("ID: " & Session.SessionID & "<br>")
Session.Abandon()
Response.Write("ID: " & Session.SessionID)
End Try
=========================================

The first Response.Write statement spits out the current
SessionID....that's fine but the second Response.Write statement also
spits out the same SessionID as the first Response.Write statement had
produced.

Shouldn't the second Response.Write statement generate a different
SessionID since I am abandoning the Session after the first
Response.Write statement?

 

[sloan]

It ~~should after you do a redirect.

Session.Abandon will leave the Session variables there, for that "page run".

...

But there are times when even a Response.Redirect doesn't work.


.....................


There are lots of posts about it:

http://www.google.com/search?hl=en&q="Session.Abandon"+SessionID

 

[Aidy]

The session is only actually abandoned when the page stops executing, not
right away.

 

[MasterGaurav \(www.edujini-labs.com\)]

The session is only actually abandoned when the page stops executing, not

right away.

I agree.
Also, the client must be notified to delete the cookie


--
Happy Hacking,
Gaurav Vaish | www.mastergaurav.com
www.edujini-labs.com
http://eduzine.edujini-labs.com
-----------------------------------------