re-fire global.asa ?

Last week I was storing my variables in a database and retrieving them on
every page of my application, but this week I want to retrieve them only
once and store them in an application variable. This works, but if I have to
change one of the variables, the application variable remains unchanged
until the web server is restarted, thus re-firing global.asa.

Is there a way to force global to fire again, refreshing my variables?

Evertjan
Sun Oct 10 14:54:16 CDT 2004

Ted Dawson wrote on 10 okt 2004 in
microsoft.public.inetserver.asp.general:

> Last week I was storing my variables in a database and retrieving them
> on every page of my application, but this week I want to retrieve them
> only once and store them in an application variable. This works, but
> if I have to change one of the variables, the application variable
> remains unchanged until the web server is restarted, thus re-firing
> global.asa.

Perhaps next week ...

Seriously, I do not believe you cannot change application variables in real
time. My active visitor counter would not work, if that were true

> Is there a way to force global to fire again, refreshing my variables?

Yes, but you will end all the active sessions.
Your users will not like that.

--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress,
but let us keep the discussions in the newsgroup)

dlbjr
Sun Oct 10 16:47:38 CDT 2004

Ted,

They are application Variables. So when you make changes to the variables and save to the database
just do this.

Application.Lock
Application("VAR1") = var1newvalue
"""
"""
"""
Application.UnLock

This will update the variables and not loss the session variable data to connected clients.

--
'dlbjr
'Pleading sagacious indoctrination!

Ted
Sun Oct 10 20:35:27 CDT 2004

Thank you, works great!



Ted



"dlbjr" <oops@iforgot.com> wrote in message
news:ORzn5KxrEHA.3608@TK2MSFTNGP14.phx.gbl...
> Ted,
>
> They are application Variables. So when you make changes to the variables
> and save to the database
> just do this.
>
> Application.Lock
> Application("VAR1") = var1newvalue
> """
> """
> """
> Application.UnLock
>
> This will update the variables and not loss the session variable data to
> connected clients.
>
> --
> 'dlbjr
> 'Pleading sagacious indoctrination!
>
>