>That is excellent suggestion.

Excellent suggestion, but it didn't work <g>.

> I checked thuroughly. that wasn't the case. In my test the only data changed was to a cursor i created in memory that wasn't even buffered or associated with a dbc or de property, just changed as the Load occurred.

Does the form really have a private datasession?

>It also didn't matter that I had just this form up alone, or this form plus 4 or 5 others also. All the forms are from the same class. Just this one form behaves this way. Specifically, I close it and the datasession doesn't go away. The views which are buffered go down OK. The tables are left behind along with that 1 cursor made on the fly.
>
>I'm going to try alternative methods to work-around.

Try to close all tables manually. Having a private datasession should do this automatically, but who knows. Perhaps you will even get a relevant error message, why you can't close the tables.

I am not sure which would be the appropriate method for this. Destroy() or QueryUnload(), probably.

Hilmar.