Hi Pavel

PMFJI, but I think, I know your problem. Have a look at the RThreshold property. As long as this is set to 0 and you haven't any other type of handshaking/signalisation on the Comm port, you'll see simply no firing of the OnComm event I'd say.

Once you set this to let's say 1 or any other number, onComm will fire, when the number of chars in the buffer reaches this threshold. Have also a look at the NullDiscard, that stops CHR(0) from beeing reported. In the OnComm you should place a DO CASE/ENDCASE to answer appropriate to the different possible CommEvents that can happen. The online help has a sample in VBA for that, but the translation is rather easy.

HTH
Markus




>I saw this (all FAQ and KB).
>The OnComm event maybe fire, if I send "ati" like in this example (I don't try it), but I want to send another data.
>All my problem is - how to check (in VFP) clicking of external button.
>Pavel