I think you are confusing application and session. Sessions survive the
lifetime of a user connected to the application. The application outlasts
user sessions. It would make more sense, as Ray suggests, to populate these
variables in application_onstart.
--
http://www.aspfaq.com/
(Reverse address to reply.)
"MEM" <> wrote in message
news: om...
> Hello,
>
> I'm using application variables for a web based sales tracking
> application. I use the variables for stuff like connection string,
> database name, etc. I store the values in a asp file that is included
> in a login page. The assignments are in a routine/procedure that I
> then call on the login page. This is done everytime a user connects to
> the login page.
>
> So, what's happening to the variables? Are they being overwritten
> everytime a user accesses the page? I'm not checking for the existence
> of the variables. I just call the routine everytime the page is
> accessed. I know the values are shared for all users but, I was
> wondering if I should check for the existence of the variables? Will
> it free up resources? Should I be using locks?
>
> Thanks.