>>>
>>>The page's life... I mean the time it takes to render it... thus is only while it's being rendered. Not after the is sent out to the browser.
>>
>>OK then I misunderstood. Save it to a session var then (maybe just ADO.GetRows).
>>Cetin
>
>SOrry for being so dense but I don't see the advantage of using a session variable. The results of the query are only going to be used for that one page, thus scope of retrieved data only needs to be page-centric rather than session-centric. Subsequent pages will result in different queries being generated. (Same query, different unique ID criteria for the where clause).

OK Mark,
To tell it in another way,
RS.Close
Connection.Close
Save whatever way and whereever you wish (ie: might be ADO.Stream but release connection ASAP).
PS: Maybe we're having communication problems because I don't quite understand how ASP works. If it's releasing connection implicitly no problem then.
Cetin