Just to add,

Another nice thing about using VFPCOM.DLL for events binding is that it does not require the event receiving class to be defined in code. The class can be a visual class and all you need to be able to bind it is to add the corresponding method.

BTW, VFPCOM.DLL works in VFP5 too.

Waiting when VFPCOM.DLL will be fixed for VFP7...


>John and Larry,
>
>Very educational thread!
>
>John: Would I be correct in assuming that VFP 7 applications can use VFP 6's VFPCOM capability? If so, do you know what additional files one would have to ship with a VFP 7 setup utility if one was using VFP 6's VFPCOM capability? If one wants just to trap specific events, then my understanding is that you recommend going the VFPCOM route vs. the Implements route? (Just trying to verify my understanding)
>
>Thanks!
>Malcolm
>
>>Besides, this issue is really about simulating the With Events keyword in VB. As I see it, IMPLEMENTS/EventHandler is overkill if this is all you want to do. In my not so humble opinion, VFPCOM and BindEvents is far more simpler and efficient than dealing with the IMPLEMENTS/EventHandler mess. As I said, I tried to get a good compile, but could not.
>>
>>I understand the need and application for Implements/EventHandler. However, I reject the notion that it is a perfect substitute for VFPCOM/BindEvents.