I have noticed the same behavior too. An alternative is to download VFPCOM from MS site if you dont have it and use VFPCOM.BindEvent() to bind the OnComm() event to a method you have defined. This work, but is ugly and more error-prone. A better alternative is to build a COM in VB. This is what I've done in my last project and it work like a charm.

HTH

---

>I am using Mscomm32.ocx with win2000 and have noticed that the oncomm event does not fire !!! Does anyone has a fix for that ?