Jim,

The MS documentation does do very little to cover this critical issue. I spent 5 pages and a couple of sample programs discussing it in the PTF-OOP book. And it does bite most everyone when they start using object references, it's a lesson once learned never causes a problem again.

If you want some extra level of assurance your objects are destructing you could always have every object register itself with an ObjectManager in their Init() and unregister in their Destroy(). You could then query the ObjectManager to tell you what objects are still in memory. It won't do squat to tell you who holds references but you'd at least know what was being held in memory.

>While I agree that the code is doing precisely what I tell it to do, and I even state that it is executing according to the documentation, this *DOES* consisiute a "memory leak", albeit within VFP only, for someone WHO DOES NOT KNOW THE "RULE" OF 'dangling references'.
>
>And I'm sorry that I messed or forgot your prior about the accuracy of SYS(1016).
>
>As I'm sure you will agree, the call for help with either 'slowdown after longish running' or 'my form won't go away even though I release it' or 'how can I run out of memory with my small application' or other similar ones come up frequently enough to show that lots and lots of people never saw the bit in the Developers/Programmers GUIDE about memory staying occupied if any 'dangling reference' remains.