Timer control issue

[DSummZZZ]

I have poked around some using google etc, but haven't seen any reasoning behind another issue I'm having.
A Timer control on a VFP 9 form works fine on an XP or Server 2003 machine, but seems to quit working (Timer event stops firing at the set interval) on a Windows 7 machine. It will run for quite a few minutes, or even for a few hours, then just stop firing.
Anyone else seen this behavior?


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[DSummZZZ]

...default code of any new project, no matter if test or production.

Uh, no. When I am developing an app, on the rare occasion my app has an error , there are times I want to see the dialog pop up at runtime so I can click on suspend, then 'Fix', which closes the form and takes me right to the line of code with the error. I consider this to be a real time saver during development.

You searched for "Interval="

Gee whiz. Now you're getting nit-picky. Of course I searched every single occurrence of 'interval' in the entire project just to make sure. I quoted it that particular way for readability. I'm not a beginner.
Also, there is no 'SetAll' in the app. Especially with an interval property specified.

In short, there is nothing in this particular app (or any of the several other timer based apps I am using) that would make the timer just stop. Again, let me state: This app, as well as several other applications I have written that have been in production for years, will run for days or weeks on end if they are running on a computer with an operating system that is NOT Windows 7.
So, from what I see here, no one besides Herman Tan (who testifies to their unreliability) and I, has seen any issue with native VFP timers on Windows 7.

Again, thanks everyone for the replies.


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[Olaf Doschke]

Dave,

I know you're not a beginner, we're already that far into analysis, that I clutch at every straw.

All I can conclude is, the Interval of a timer doesn't get 0 on it's own, and yes, I don't see Windows7 introducing new unknown timer issues.

You can have different oppinions about error handling. The native error message does not tell about line number for example. In my default error handler I do also have a suspend to go into live debugging, this is not a standalone feature only the native system error message has, you can roll your own, better. And once you have that, you'd not want to miss it.

What can be suggested as solution? How about adding a timer checking the interval of your current timer, resurrecting it, when it got stuck? If the watch over each other, that might work, unless there is something stopping all timers at the same time.

Bye, Olaf.

 

[clipper01]

you could try the cpptimer.fll from

http://www.bbcontrols.com

, has 50 independent timers. I've had to use this on some occasions, far as I recall it was if user had left a messagebox response pending, that killed the vfp timer