Hi Chuck,
I believe Kevin is asking about Queues in reports - your original post seemed to imply this was in report procedures.
For browses you cannot use queues, but for reports you can.
>> My concern is the use of RAM - there may be 25 different users logged in at any one time with each user having 10-15 memory tables created for their session. How do I remove the memory tables from RAM when each session ends?
you would want to delete all the records from the memory table that belong to a session, when the session ends.
>> And how do I know when a session ends?
the NotifyDeleteSession method in the webHandler will be called - you can access self.sessionid in here, but you can't access SessionValues or any other session related data. In your case you have the session id, and that's all you need to clean up your ancillary files.
>> What is/are the best ways to manage the RAM in this scenario?
Obviously the memory table approach may be faster, but will indeed use more memory. you will need to observe, and test, to see if memory use is becoming a problem in your application. It's impossible to predict if it will or won't be - that will depend on many other factors in your app.
If performance is acceptable using TPS then I'd probably carry on using that to improve scalability.
cheers
Bruce