Cool, it stays on the server. This will rock much.

Now... if they abandon, then yes, I have that variable for 20 minutes.

As a matter of clean up, I could set that session variable to "" on any page that doesn't require that I keep it, or any page that indicates that the user is finished with the reports. For example, if the user is done with the report and clicks on the home link, the home asp could clear that variable. And if that variable wasn't around before the user clicked home, no harm done.

I don't imagine having a lot of users at any given time. It is for an intranet application. I do imagine having a lot of DB entries. Just yesterday I was playing with a sample that had 1500 incidents. That is about 3000 DB records that have to be pulled every time and scrubbed to get the open and close times for those 1500 incidents.

Now, that work could be done once and the 1500 incidents could be saved in the XML in memory (and not on the disk).

I feel like I am just playing with the tip of the iceberg of possiblities.