Let's take just one example. I'd look into why they're being created, first. Are you using SESSION object? Or do you use SET DATASESSION TO in production code? Private DataSession forms, reports? Default? Mixture? If you can zero in on one example, that you can reliably duplicate, then we could offer some suggestions. Otherwise, we'll just be guessing. Not that that's ever stoppes us in the past, but it would help focus the replies.

I am only talking about private data sessions here and I don't use the Set DataSession to command in production code. It looks like to me that parent tables from some of the local views used in the data session are left open. Also I seem to have a cursor or two from some on the fly query (which I know I shold have taken care of).

I was thinking of just determining what data session the form is using then in the destroy method of the class, check if a private data session and then close all the tables in that data session -- make sense?

Kevin