There are 2 session events in global.asa: Session_OnStart and Session_OnEnd.
Session_OnStart will trigger only once per session: That is when the first asp page of an application is hit, doesn't have to always be the same page (should be).
Session_OnEnd will trigger when a Session.Abandon is incurred or after a session times out.
What's a real shame is the unreliability of those events firing when they should. It's not a good idea to put a vital piece of code in the global.asa file cause you just can't trust it to fire.
[small]"I see pretty girls everywhere I look, everywhere I look, everywhere I look. - Band song on movie "The Ringer"[/small]
<.
Let me tell you what I am trying to accomplish and maybe you can assist in a work around.
It isn't that big of a deal.
I was going to use the global.asa Session_OnStart event to write some information about the client to a log database,
but that doesn't help me if it is only triggered when an asp page is loaded.
The work around might be when any page (.asp or .html) in the web site is accessed for the first time, the session begins and the information is written to the logging database.
My suggestion to myself is to put a bit of code in all of the main pages for the onload event of the <body> that would call the script to run.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.