>It did help. I now have a (too much) reliable OnComm() event. I said too much, because it fire many times for each new string in the Input buffer.
>
>I inserted a DEBUGOUT in the OnComm() event and it give me a series of "ATA" (when I ask the modem to answer the phone), a series of "CONNECT", etc. It doesn't give me problems for now, but I wonder why it fire so many times for a single event.
>

There are a number of events besides the receipt of a character that trigger the OnComm event; take a look at the OnComm Event example in the MSDN docs (yeah, they're in VB...but it's easy enough to figure out.) If the RThreshold set for the comm instance is one character, then it'll be triggered once per character received. If the port senses a change in the port being ready to send, it'll pop the OnComm event. The trick is to only respond to events that you've an interest in, and ignore everything else.

>>Hi Sylvain. Does Message #257005 help?