>Sometimes I have forms with private datasessions where the Datasession will continue to live on as "unknown" after the form has been released.
>
>These "ghost"-session sometimes have tables open, sometimes not.
>
>I must say, I'm normally NOT using the DataEnvironment. Most of the DataAccess is done via BusinessObjects and it's their duty to decide witch table to use when.
>
>I could deal with the issue by adding some cleanup-code but this still does not tell anything about the "WHY?". Normally releasing a Datasession should also release all its tables (and luckily this is exactly what happens most of the time).
>
>There are no transactions or tablebufferings in the context.
>
>I'm not sure how to narrow this down. Any Idea?

hi Frank

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

Form.Property = Form.Grid1.Column1 && gridcol cannot release, hence grid cannot release, hence from cannot release

(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