>>Can you determine how much time does it takes to the timer event to be executed?
>>
>>If you click on the combobox and wait more than 1 second, does the combobox respond or not? The same thing for a longer time: 10 seconds. Theoretically, the combo should respond after the timer event is done. Since the timer event has low priority in Windows, the click event should be executed before the next timer event even if the timer event is longer than 1 second.
>>
>>Try to see if you can reproduce the problem with an Interval of 2000-5000 for the timer.
>>
>>Do all your tests with only one app opened in Windows. Since there's only one timer (interrupt) on one computer, this is a VERY shared resource.
>>
>>I wrote a VFP app that controls 32 terminals via timers. I had a lot of problems, but never something like that one you have now, so I'm very interested to now what is all about.
>
>Vlad
>
>Did some more testing in 95. The 'flubs' 'seem' to occur about when the Timer should be firing. Very un-scientific but I set it at 5000 and 'about' that time it would not work and then work fine a few tries and then not work.
>
>You may be right about resources -- I am using a BUNCH!
>
>Tom

You must always think that all (on one computer) timer events procedures cannot use more than 100% CPU time. And Windows must also run the mechanism for more timers (on only "hard" one) on the same CPU.

This is way timers are not recomended. Also, it's good to know the timer events have the lowest priority (as far as I remember). That means you can't build a reliable process on timers.

Vlad