>>I think it's a bad design in VFP that such an explicit call (AEVENTS()) is required when
>>the same information (and more) is very likely almost always needed (along with
>>some user-defined parameters being passed as per a custom basis).
>
>As someone who has used BindEvent() extensively, I disagree. I find that I rarely
>need to know which object triggered the call. If you look back at my presentation,
>I think you'll see that out of all my BindEvent() examples, only two or three call
>AEVENTS().


I think not knowing what a person doesn't have prevents them from realizing what's possible were it easily available.