>George,
>
>>If I were to hazard a guess, I'd say the problem is caused by a stack overflow. If I can eliminate that by re-writing the code properly, how can I (or you) say it's a bug?
>
>You really don't understand what is happening? I know what is happening, and I can say what is going wrong in VFP 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 VFP 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!!
>
>Walter,

No you're not right. See my response to Fabio.