Erik,

Thanks for the info.

The reason I had this question is that on the Wiki Sylvain Larin had posted some info on the MSComm control stating that OnComm events were not reliable and needed to be binded to using VFPCom.BindEvents(). I then posted a response of "How so?" to paraphrase. To which Ed Rauh responded:

If you don't bind something to the OnComm? event inside VFP using VFPCOM, the OnComm? event never fires inside of VFP, so you're left with polled comm I/O. VFP doesn't know about the event unless you bind something to it... EdRauh

I think I am missing something or their posts only refer to subclasses of ActiveX controls compiled as Automation servers. The way I use the control is as part of an OleControl added to a Container using the Class Designer. If I understand your message you are saying that as long as I don't use this as an Automation server and try to attach code to the OnComm Event from outside my container I should still be able to depend on the OnComm Event.

Please correct me if I'm wrong. I want to get a handle on this.

Thanks,
Todd