Session Variables ......

[OptimusPrime]

been working on a project now for almost 12 months with about another 5 programmers and we have been testing the software on our own machines (each programmers computer has its own copy of IIS)

but we have been storing user specific variables in session variables .... not knowing that these are global to the system so .... when another user logs in the variables are over written !

can n e one suggest a place to store them ?

or suggest a way around the session variables so we can make them user specific

many thanks
Optimus

[VBCrazyCoder]

My understanding (at least from ASP 3.0) was that Session variables are user specific. Do you mean your Application variables are over-written? I used Session variables all the time and never had that problem - no other user could access another users session variable. In fact, that's why they call it a Session variable - it only exists for that user session.

[OptimusPrime]

kinda getting round it @ the moment

we set the system variables up as application variables n only 12 months down the line has this been noticed / or started causing a problem

we're now working on setting the variables up as session variables rather than application variables .... so they remain user specific

but were now encountering problems storing the session variables on SQLserver and enabling the session state but hey lifes never easy with dot net

[MrGTI]

Ask this in the ASP.NET forum. You'll have more luck getting an answer.

[Lethal]

You only have to use sql server or the state service when you are serving your pages up in a web farm architecutre. Yes, you can still us sql server or the later, but you will see a performance degration.