Thanks for the clarification, Dave.

~~Bonnie


>>Actually, now that I think about it a little more, I don't know why it would necessarily *have* to use a cookie when you are using SQL Server. The web server knows about the fact that you are using SQL Server, as you need to include the SessionState mode in your web.config.
>>
>>Are you sure about this?
>>
>
>The contents of the session stay on the server side (in proc, out of proc, or sql) but the session id has to travel between client browser and web server on each request. It can do this either in a cookie or url.