>>>Maybe, but VFP's timers aren't that accurate. Setting the interval for 25 hours would probably be more like 29. You can test it, to see if its not as bad aas I thought, and my method would be more accurate. YMMV
>>
>>You're extrapolating without any basis. I found them surprisingly accurate.
>
>I will jump in since I have been researching this issue. In Chapter 10 of the Programmer's Guide: "The system generates 18 clock ticks per second, so even though the Interval property is measured in milliseconds, the true preceision of an interval is no more than one-eighteenth of a second."
>
>Also:
>"The interval is not guarenteed to elapse exactly on time. To ensure accuracy, the timer should check the system clock when it needs to, rather than try to keep track of accumulated time internally."

All that means is the Timer (in this case) will "probably" fire at (about)25:00:00:05.

In "very low interval" situations (eg. 10 ms), VFP does not queue timer events that are not handled (in my experience). So, if you were "counting ticks", it wouldn't be accurate.

That is not the same thing as waiting for ONE Timer event to occur after a given Interval has elapsed.