>>>Can not figure out your code but did it anyway. No change.
>>>
>>>Thanks Anyway,
>>>Tom
>>
>>Ok. What do you mean by "Timers not letting combo boxes work 100%. The selection was not working as good as w/o a timer."?
>>
>>In any case, disable your timers before detroing them. It will save you a lot of problems. Another good idea is to release them efectively (using RELEASE command). I can't figure yet what's wrong inside VFP with timers and it's really hard to make test since there are some strange behaviors very hard to repeat. For example: Netscape will generate an illegal action almost every time if you don't disable all timers before destroy them.
>>
>>Other strange behaviors also available. :)
>
>Vlad
>
>Timer is set for 1 sec increments (1000). The combo boxes do not work 100%. Sometimes you need to click a selection 2 or more times to choose it, sometimes not.
>
>Thanks
>Tom

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