Hi Stewart,

> I'm always careful to include in the Destroy method a line of code that will store NULL to the datasession object property so there are no dangling object references.

That works in 99%. You get a bit more stability when you set the property to NULL before the Destroy event fires. Usually there aren't many problems with simple scenarios involving just two objects and two classes. The more classes, objects and inheritance levels are involved, though, the more important becomes the proper order of releasing objects and the less likely it becomes that VFP happens to perform in exactly this order. By removing all reference before VFP even attempts to start clearing up multiple objects, you can remove one source of problems completely.