<< Session are fine if you really need them. But if you don't you're wasting
<< valuable resources on the server. Sessions also don't scale to multiple
<< machines, so there are other issues.
<<
How do you know if you actually need them?


<< In general I don't use sessions at all. Rather I use a single Cookie
<< which *I* manage rather than ASP and then store my session info
<< in a database. If you use ADO there's more overhead there, but if you
<< use a VFP COM object the overhead is actually less than a session.
<<
I thought you needed Sessions turned on to see cookies? How is is that you manage it yourself?

I do in fact use ADO but would consider using something else. Is there a way to create an object at the session start that can carry information throughout the session? Like if I created some object in VFP or VB that created the properties I wanted to carry as session vars, and updated to a table when I was done?


Thanks for the information...
Michael