Dear waterbug,
Tim wrote on 16 mrt 2005 in microsoft.publi c.inetserver.as p.general:
E: Why do you think global.asa has anything to do with it? Try the
same without any global.asa present.
W: My app won't work without global.asa present. I rely on many
session vars for db connectivity and resolving security.
Session_OnStart is caled once when a new session starts. This means,
if you browse the site, Session_onstart is only called the fist time
you go to the first page.
Tim is right. [also on the quoting issue, but that aside]
The fact that Session_OnStart is called at the beginning of every new
session does not mean that global.asa is run. Global.asa runs only at
the application start. Session_OnStart sub is helt in memory.
I suppose your problem is a session problem. If the session is not helt,
because the browser does not allow a ram-cookie, every page is a new
session with a new call to the Session_OnStart sub. ASP pages are always
a session.
However without relevant code we cannot envision the exact nature of
your problem.
btw, did you try to debug?
=============== =========
I rely on many session vars for db connectivity and resolving
security.
And you initialize those session variables [we are talking session() ?]
in Session_OnStart ?
Why?
They can more easily be initialized on your entry page, easying the
debugging process. Or if you have multiple entry possiblilities, with a
include statement.
That way you can have administrative entry using a different security
appoach for your own purpose. Or differnt [open?] pages in another part
of your site.
--
Evertjan.
The Netherlands.
(Replace all crosses with dots in my emailaddress)
