Hi Joe,
FWIW: I don't know if this is relevant to your situation but check out "Autoyield" in the VFP documentation. It helps keep VFP code and windows events discreet.

Steven-

>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?