Hi Nick,

I discussed this issue with my colleague, and he explained to me, why does it happen. This is the second case, which you mentioned.
If the form invokes creation or instancination of an object (in this particular case custom class ErrorHandler), this object catches DS and untill it releases, the DS doesn't go away.

In our conversation I called it VFP-bug, but he called it Undocumented VFP feature...

It's good, that you mentioned David Frankenbach's utility. It seems to me, that I saw today, that somebody else referenced it as a best utility of Files section, or it could be GT utility with similar name. I don't remember right now...

Anyway, I'll download it in next occasion.

>>
>> I was working on the project, which my collegue started. Recently I found, that these form doesn't clear after itself (leave Unknown(2) DS) despite the fact, which it uses Private DS and all properties in DE are default. How could it be and what do I need to check?
>>
>> TIA
>
>Hi Nadya,
>
>There may be several reasons. I think the most common are:
>
>- One or more tables/views were not closed because of uncommitted changes.
>- Form was not completely released because of dangling references to some objects
>
>To check the last one you may try David Frankenbach's utility in Files Section
>file#9466 "ObjRef-finds dangling object references"
>
>Nick