>>>That's really odd. I tried adding the comment, and BindEvents worked. I can bind to other event methods like QueryUnload without any code in those methods, I wonder why it only works for the destroy method when code is included in that method? Does FoxPro internally look at the object code, and decide not to issue certain events based on code existance, or does the BindEvents() call fail implicitly if you try to bind to a destroy method with no code?
>>>
>>>At any rate, thanks for the tip
>>>
>>>Brian Vander Plaats
>>
>>Sergey give to you the official answer.
>>
>>In other words VFP don't call Form::Destroy,
>>and then the routine that catch this call
>>and check for bindevents is not called.
>>When you add a char to Destroy,
>>you force VFP to call Destroy and
>>then the BINDEVENTS can happen.
>
>And it was discussed long ago that the Help should tell us which have this characteristic, but alas it seems nothing yet.
>I suppose it's good that every person has to find out for himself.
>
>>
>>Fabio

Hi Jim,

My next free time project is: rewrite VFP Help!

Another big mystery!
Why VFPT don't redefine When/Valid/Destroy ... as a Void routine ?

Fabio