Absolutely, and Bindevent() is a fantastic advance isn't it. It's awesome for decoupling code dependencies amongst objects.

>Now we're talking. Kudos to the MS FoxTeam for this.
>
>>Ramil, you can use the new AEVENTS() function to help in debugging. It identifies all existing Bindevents.
>>
>>>>The first one. (first f1, then f2, then After)
>>>>
>>>>With nFlag = 0, it would be:
>>>>>- oF2.cmd1.click
>>>>>- oF1.cmd1.click
>>>>>- wait window 'After the events'
>>>
>>>Thank you. IMO, this is a very radical feature in VFP8. Although, this may cause some kind of debugging nightmare if the BINDEVENT() is lost in the menagerie of codes. Sort of reminds me the VB GOTO.