>I concluded the process was doing too fast - the powerful speed of Visual FoxPro. :) So, by putting DOEVENTS, this seems to have fixed the problem.


MScomm32 also needs DOEVENTS at times when FoxPro code is running, and the control does not get enough events to process OnComm events. The trick sometimes is to place enough DOEVENTS to keep things going, but not so many as to slow everthing down. Also, since DOEVENTS includes all windows events, your code must be interruptable (timing related) at the point the DOEVENTS is placed.
I wonder if other ocx's are affected ?