OK, you are clearing it - good.

I don't know if it's an ActiveX problem as much as VFP's handling of ActiveX events in this case. I have seen one app where scans were coming in at about one every 5-10 seconds and it exhibited the same strange behaviour. There was a ton of processing being done behind the scenes, and occasionally a scan would double up as yours seems to do. Somehow, events were missed. Eventually, I said 'uncle' and plopped in a 3rd party Activex and worked around the problem.

If it isn't resetting the Input property, it is an ActiveX problem. It's been in use too many years by too many developers - I doubt that is the case here.

I'd fire up the Coverage Profiler around the event and see if anything strange shows up.

>Yes, at the end of my code .pcLastReading = '
>But still how come that can happen? Dont you think it is anActiveX probem? Looks like it does not reset the Input property.