>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.
>
>Thanks again.... Rich

We have events in VFP. The Error Event automatically fires when an error occurs. The keypress event fires when the user presses a key. In VFP, we bind code to these events in the EventMethod, causing the code to fire when the event happens. Many applications are capable of exporting events to other applications. Using the VFPCOM.DLL we can bind code to the events in the other programs, so that when the events happen, our code runs. BTW, VFP cannot generate these external events.