>>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 ?
>
>Yes, I also found that I had to put one DOEVENTS at the startup of the method and one before the Connect.

My experience with mscomm32 and DOEVENTS went so bad that instead of using this setteled for 2 timers
1 for reading char. and 1 for prosessing the message.
MSCOMM32 is not good.


Best regards

Per Simmersholm