>Hey Dudes,
>
>In one of my applications, I have TIMER objects constantly running code. (They
>are constantly reading data from various probe hardware).
>
>Buttons on forms should always be usable while the TIMERs are running.
>
>In certain circumstances, it takes multiple attempts to click buttons on the forms before the button actually registers the click.
>

I'm not sure if this will fix the problem, but I'd recommend moving your updates into one timer. If you now have one timer for each probe and several probes, then you have alot of unnecessary timer overhead. Add a method and a "last run time" property for each probe. (Either subclass the timer or add them to your form) The Timer Event code checks to see if it's time to run each probe check and if so, calls the method and updates the "Last time run" property for that probe.
You could put all of the code in the Timer Event, but using methods will make it easier to read and add new probes.
Hopefully, reducing the number of running timers will free up the event loop and get your mouse clicks working.