>>>>>I've definitely had problems in the past where the timer on a form in a 24/7 EXE would fall asleep and just nudging the title bar with the mouse would wake it up. That was like VFP 7 back in the day. I also had problems with the timer in VFP 3 or so.
>>>>>
>>>>>Anyway, we have a customer site where our app uses up to 3 timers, I believe, and it appears that they're falling asleep and not firing.
>>>>>
>>>>>No other customer seems to be reporting this, however. But, the customer says it happens on numerous machines at their site.
>>>>>
>>>>>The purpose of the timer is to see if a file hit a folder and then to act on it. I'm trying to extract the bind events in the VFP 9 Windows Events in the Samples and it, the event binding, seems to work.
>>>>>
>>>>>Anybody?
>>>>This doesn't answer your question, Jeff, but you might want to look at the Windows Scheduler.
>>>
>>>This timer is in an app that needs to consume files as they arrive, so it's not good for Windows Scheduler. BTW, I'm a big fan of Windows Scheduler for little FoxPro jobs.
>>
>>Have you considered eventbinding to check for the files arriving? For what I know one can watch folders for change. And If yo can not with VFP, do with .net.
>
>Thanks!
>Yes, I've created a proof of concept VFP form using event binding from the VFP9 Samples\Solution - New in Visual FoxPro 9 Binding to Windows Message Events.
>
>Only one customer is having this problem and changing the code would be a big job. So, I'm not sure what is going to happen.

Since timers like that considered odd all the time ....
And you need to figure out whats going on, maybe it becomes an avalanche. Something odd MS is doing.

Me would try the fast fix and skip the timer. :)