>>>>I have a small program with two timers; one timer is simply used to show the progressing of times (in seconds). The second timer actually performs a procedure every minute. It happened once last week and today that customer reports that the timer that shows progressing of time stops at various points (e.g. 43 seconds) and the program stops. It does not freeze though as he is able to click on the Stop button and restart the program.
>>>>
>>>>What could possibly cause the timer to stop?
>>>>
>>>>Thank you in advance for any suggestions.
>>>
>>>Is it possible that other (non-VFP) processing is hogging the CPU and preventing the Timer firing?
>>>Regards,
>>>Viv
>>
>>I suspect that this is what causes the problem. I will ask the customer to check the CPU if/when the problem occurs again. Thank you.
>
>We had this happen at a couple of customer sites and couldn't determine what was causing it until we setup a 2nd timer to do nothing except periodically check the status of the 1st timer and enable it when necessary. A global switch turns the 2nd timer on or off. Whenever the 2nd timer found that the 1st timer wasn't enabled or firing, we logged everything including all running processes on the system. It helped to determine what was causing the problem.

This is kind of what my customer suggested. He said "can you put a second timer to let us know if the first timer stops working". But the problem is that the timer that occasionally stops working does nothing but shows seconds progress. And when this timer stops I suppose any other timer would stop too. I kind of think this that the problem is caused by (as was suggested by Viv) some other program taking over CPU and telling my timers to pound sand :). I wrote the customer to check on the CPU usage if/when this type of issue happens again. This should confirm this theory.

Thank you.