>Gregory
>
>> There are a number of possibilities as far as I know.
>>
>> Check:
>>
>> (1) you have used a TreeView and had a Treeview error like accessing adding a
>> node that already existed (error trapped or not) see thread#853186
>>
>> (2) the form, or any object contained within its hierarchy holds an object
>> reference of an object down the hierarchy.
>> eg ...
>>
>> (3) you have created an object (which now has the datasession id of the form)
>> and the object is not released by releasing the form. So there's an object
>> left with a datasession Id of say 5. Hence Datasession #5 cannot release (or close)
>> eg:
>

scatter memo name someobj && and someobj is public && had this recently, takes time to find it

>
>No Tree, no dangling object-references and no public objects (at least AFAIK ;-) ).
>I have some objects that are form-Properties but those get released properly. I'll now
>try to realease them manually in the Queryunload(). Let's see if that changes anything.
>But I think this leads somehow in the right direction. Maybe its a problem of order
>where the form releases its Datasession while an object still does exist although the
>object finally gets released by the time the form is completely gone.
>
>Thanks so far.

Hope you sort it out

I do not think there's a problem having objects as form properties as long as they are not an object that can be addressed from the form itself, ie part of the form's hierarchy
as in : thisform.PageFrame.Page1. ... ... ....Textbox1 or so

The object references do not necessarily have to be public as long as they do still exist after the form tries to release, ie added to _screen or any other public instantiated class or so

Good luck. I know it may take some time. Oh and do share the results, maybe there's point 4)