You still can't define events in VFP... And since you cannot define them, you cannot raise them...

>Maybe I'm missing something here somewhere, but what about BindEvents and VFPCOM? Seems to me that's our replacement for VB's With Events.
>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>Hi Vin...
>>
>>Hook patterns and access/assign methods at best are poor cousins to event definition and raising. At the surface, they appear to be similar. And, if you stay in the confines of VFP (i.e., single/two tier) you are fine. Kevin McNeish's FPA article did a nice job of showing how you can "simulate" events - with an emphasis on "simulate". However, if you stray into the COM arena, the whole thing breaks down. Unfortuanately, Kevin's article did not stress this very important limitation.
>>
>>My purpose here is to let folks know about the limitations as they may be very relevant...
>>
>>< JVP >
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>
>>Hi John. Yes, the limitations are relevant and important. But, I am not sure what, exactly, John is trying to do based on his original post. Too often, I see VFP people walk away from VB thinking, oh I guess it can't be done because there's no Squiggle keyword. I didn't want to see the inverse happen in this case - as you point out, if he is trying to implement something within VFP, there may be another approach that will work.
>>
>>BTW, any word that on event-raising being added to a future version of VFP?