Hi Walter,


You really don't understand what is happening? I know what is happening, and I can say what is going wrong in Visual FoxPro internally. The object reference counter is not calculated correctly when the object reference is handled by an assign method. It is probably is decreased when the assign is called while the property still holds the reference. Since in Fabios example it is not explicitly assigned when the object reference passed as parameter is the same as the reference stored int he property it is not increased anymore. When it reaches zero, poof the object is gone, or because of the unfinished click event Visual FoxPro lost a call stack entry and causes a C5.

If you don't believe me, just ask any VFPT support member to dig into this. You'll see that I'm right!!


I know also when it is happened this:

When VFPT has added _ Assign to VFP6,
it has not moved the calls of C code that manage the reference number
to an object when the assign it is made effectively,
but is do this code when it exec the VFP external assign.

I task that to fixing this problem without to add some of the others,
or to slow down the execution is not easy for the VFPT.