>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

The OnComm portion of MSComm32 takes a LOT of tuning to function well, but will eventually work. I have one class named HighComm based on it, that will handle 4 com ports at once.