Thanks for your attention to my problem. I'd finally found the problem, but I believe this is not documented elsewhere. The problem occurs when I create an object (any object) using _screen.CREATEOBJECT in the Load event of my form. I had corrected this problem by moving the code to a higher level (application level), and the problem is no more there. Hope this could help our fellow members if they read this.

Thanks again.

juan

>>Hello,
>>
>>I have a explorer-like form (with a treeview and a listview). Form's dataenvironment contains 2 tables and 2 views. The problem is when I run the form and quit the form later, the datassion still exist, even the form has disappear from the screen. I can see the datasession as "Unknown(2)" using the "Data Session Window".
>>
>>Anybody out there have any ideal?
>>
>>The form is very (I would say) complicated, with tonnes of codes (because it behave like a real windows 95 explorer), and I have no idea at all where the problem resides.
>>
>>Thanks,
>
>Juan,
>
>I find that this happens on occasion. Is it possible that you have some uncommitted changes somewhere? Are you using buffering? In the times I have seen this happen, it's because there is something left undone for VFP to close down a table or tables.
>
>HTH