>>I'm not sure what you mean by "timers", the timer object in VFP or Window's own timer. I've always assumed that the timer object in VFP was merely a hook into the one that exists in Windows (that fires the screen saver, for example).
>
>I'm not sure about this. I also believe that timers in VFP are a little "something else" than the OS timers, but I don't really know what's behind the scenes. I don't know how a VFP timer is implemented internally.
>
>>Is this correct or are we talking about two different things?
>
>1. Windows timers: they are different between Win3.x and Win95. That's sure.
>2. VFP timers: the same as above.
>Some differences are:
>- A timer always stops when Enable = .f. in VFP3, but not in VFP5
>- A timer always stops when Interval = 0 in VFP3, but not in VFP5
>- A timer don't fire in VFP3 when a menu is opened (other actions as well), but it fires in VFP5
>- The minimum timer interval is about 50ms in VFP3, 1-2ms in VFP5
>- The average interval is much more reliable in VFP5 than VFP3 (the real interval is almost never exactly the one you set in the Interval property)
>There are many other differences. Basically, when passing from VFP3 to VFP5, any timer must be retested very carefully.
>
>Anyway, timers are more reliable in VFP5 (except that the only sure way to stop a timer is to destroy it).
>
>There are also differences between VFP5 timers on Win95 and WinNT. Ie: more reliable on NT.
>
>Vlad

Vlad,

Given the relationship between Windows and any application, I would be astounded if the control was anything but an encapsulation of Windows timer functionality. Again, this is a guess, but I think what we're seeing is differences in the implementation of the control rather than VFP. I think that the way we could tell this is how the same control reacts under VB.

George