Erik,

I pulled this post out of the archive and thought you might be able to help me. I was wanting to know if there is any documentation on how VFP processes events. I have a vague understanding of the Windows message loop but am curious to know how VFP manages when event method code is called and how it reacts differently to different event sources. I've tried MSDN but couldn't find much.
Any ideas?

Thanks,
Todd

>>Thanks again Erik for your email. What I really need to grasp is the CONCEPT of event notification and how the VFPCOMM.DLL extends the functionality of VFP to provided this feature (service?). I *think* I understand that the WinFax SDK is an ActiveX Automation Server... by coding the statement
>>
>>SendObj=CreateObject("WinFax.SDKSend")
>>
>>I can create an object which allows me to "tap into" the functionality of an external application (in this case, a fax engine) via the mechanism of exposing its properties, events and methods. ALL my "communication" with the WFP SDK, up to now, has taken the form essentially:
>>
>>1. send request to WFP (by calling one of its methods.
>>2. receive response and process accordingly.
>>
>>It appears that EVENT NOTIFICATION will allow me to in effect do just #2- receive a response from WinFax WITHOUT me specifically requesting it. If you'd be able to confirm my understanding of this concept, or possibly suggest some books or papers (maybe intro to ActiveX or COM/DCOM??) that would be a great help.
>>
>
>You've got the concept. VFPCOM builds a "tie" between the events raised by an ActiveX control, and the methods of your custom object (usually originally built with ExportEvents, but not necessarily).
>
>If you have an ActiveX control or other COM server that has an event named "Completed", you can build a Fox object with a method named "Completed". Using VFPCOM, you can "bind" your completed method to the control's completed event, so that your code runs when the event fires. The Help file that comes with the VFPCOM download has several examples of this.
>
>Keep in mind that with ActiveX controls that you can drop on your form, you can also do this by just putting your code in the events of the control. But many COM servers don't have a userinterface, or can't be instanciated at design time through with VFP, and these are the ones that require VFPCOM to bind events to.