Have you verified that the oncomm event is always firing? I ran into a problem with it not firing at times, so I had to manually bind events using vfpcom. I got the idea from Sergey in a post. He pointed me to this article:
http://fox.wikis.com/wc.dll?Wiki~MsComm32~VFPYou can also call the oncomm event manually after issuing your .output= command to see if it is a problem of the oncomm event not firing, or data being lost. I also had to fiddle with the mscomm properties to get them right for my purpose. How are your properties set in the mscomm object and what is your code in the oncomm event? It would help to see it in order to help.
Tracy
>I use MSCOMM - onComm event to reading data from comm port.
>
>Problem is, onComm event sometime return incomplete data. Some data was lose.
>
>Does MSCOMM able to handle fast data communication? Or any other recommended.
>
>TIA.
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
