MSComm does work correctly, it's VFP that has problems catching all the OnComm() events that MSComm generate. You are better off writing a COM object in VB that does the communication part. That's what I did and it work like a charm.

HTH

---

>After much testing I think I can say that the mscomm oncomm event doesn't always fire when it is supposed to. I am implementing a nonstandard handshaking method. The control is a receiver. I have handshaking is turned off. RTS threshold is set to zero. I require 4800,e,7,2. Mscomm should wait for CTS to change to fire. Mscomm should sit and wait till string 'q+chr(4)' is sent to it. As soon as the sender does that it should ping it's RTS line which it does and the receiver watches for CTS to change. Then the receiver sends it's ACK. MScomm never sees this CTS change half the time. I can't figure out why except that mscomm is not written well enough to handle this handshake method. Is there a better control somewhere that I can use?