Here's the overall structure of a program:

PROC main_job
private poLog
poLog = NULL
main_job2()
poLog = NULL                     && <== here the Destroy() fires again
RETURN

PROC main_job2
     poLog = someobject()
     RETURN                     && <== here the Destroy() fires first

The object has cleanup code in its Destroy(). I'd expect the Destroy() to fire where I set poLog to NULL again. However, it also appears to fire on the RETURN of main_job2. Why?

But there's a far more serious problem. Within the second Destroy() the internal memory space of VFP gets screwed up totally, ruining certain variables. This happens on the line of code where variables are declared LOCAL (in the Destroy Event).

Anyone here familiar with this quirck/bug? Is it my misunderstanding of some concept?