>Have you tried using cookies? The cookies would be available from all web apps. This would eliminate the need for maintaining state with session variables or session classes.

What about browsers that don't support cookies or that have disabled cookies? In those cases, either the app will always think that there is no value and probably will not function correctly.

>
>><< PMFJI-
>>
>>No problem...
>>
>>
>><< maybe I don't understand the problem, but couldn't you get away from session << vars altogether by implementing a generic session
>><< class that stores all this stuff for you in data files? What could this 3rd << party solution do that you couldn't write yourself?
>>
>>To the best of my understanding, classes instanciated on IIS do not persist across pages. Therefore, if you were to build a class that saved session information, you'd have to build it so it read from a database, text file or the registry. This is certainly possible, but I, like most developers I know, am pressed for time.... :-)
>>
>>Unfortunately, the real crux of the problem is, again, a flaw in an M$ product... Oh well, we've worked through these before... (and will again)
>>
>>Thanks for the reply...
>>Michael