I want to make an entry to the database when someone logs out of the site or their session times out. The following code located in the logout.asp file works fine when someone signs out, but this code in the global.asa file does not make an entry into the database on session timeout. When Session_OnEnd fires, does the SessionID still exist, or is it destroyed before the Session_OnEnd fires? Any other ideas?

Rich Hoffmann



Sub Session_OnEnd

    dim adoConnection
    set adoConnection = Server.CreateObject("ADODB.Connection")
    adoConnection.Open("DSN=RLCMembers")

    adoConnection.Execute("UPDATE LoginLog SET DateTimeOUT = Now() WHERE SessionID = '" + Session.SessionID + "';")

    adoConnection.Close()
    adoConnection = null


End Sub

__________________
Ego is a faithful friend; He stays with us all the way to the crater.

The SessionID still exists, but the problem is with the limitiations of Session_OnEnd - you can't use Server.CreateObject in there.

Can I use Server.CreateObject in Session_OnStart? Assuming not, do I then Server.CreateObject elsewhere when the site loads and never null it until Session_OnEnd? Is there a problem with leaving it created like that? Can I open and close the connection in Session_OnEnd?

Thanks,
Rich

Maybe there are some workarounds in here. http://www.aspfaq.com/show.asp?id=2078

Maybe you can just use CreateObject instead of Server.CreateObject?

Most folks steer clear of Session_OnEnd...

hth
Phil

Like Phil says, Session_OnEnd = useless.

It doesn't fire reliably, if ever. I've never gotten it to work. The best you can really do is use the logout page that works.

Of course, this could also provide you with some statistical data. Any entries in the database that don't have a logout stamp, and are past the session length timelapse are users who didn't use the logout button! :)

From a symantec point of view, unless the use clicked "logout", they didn't really log out, they got booted out. :D

Peter
------------------------------------------------------
Work smarter, not harder.

I am wanting an easy way to see if it is safe to upload a new version of the database to the website. I was hoping to do that by looking at my "login" sheet, showing the login and logout time of all users. Since that depends on the user loggin out since Session_OnEnd doesn't work, I'm wondering what a good method is of seeing if others are logged into the system. I have seen the "user counter" sample program several places, but it also relies on Session_OnEnd. Will the below work any more reliably than what I have tried above?

sub session_onStart()

    application.lock()
    application("SCount") = application("SCount") + 1
    application.unlock()

end sub

sub session_onEnd()

    application.lock()
    application("SCount") = application("SCount") - 1
    application.unlock()

end sub

sub application_onStart()

    ' don't need a lock in onStart()
    application("SCount") = 0

end sub