RE: Searching for the cause of a dangling reference.

Hi Christof, No Transaction. All objects being created are LOCAL and specifically set to .NULL. Only one is being added to a form property, and set back to .NULL. at the end of the creating method. It is used by 2 called methods. Wrote a piece of code that added a log in the init and destroy of

RE: Searching for the cause of a dangling reference.

I'm tempted to start searching in data session 0 to seek out what is causing this data session to stay open. I gained some insight on how to get there from SWFox 2006. Before I really go there (not knowing if my answer is going to be there). Does anyone have another idea for getting to

RE: Searching for the cause of a dangling reference.

Hi Tracy, A data session might also stay open if you've started a transaction in that data session. Are you adding objects to _SCREEN or are you creating global objects anywhere else than in the main program? If you create those objects in a private datasession, the datasession stays alive until