>Are you sure ? As I recall correctly and have used in several programs, Timers also fire when VFP does not have the focus.

I think you're right ... at least with Win 98, etc. Maybe Win 95 might not be as friendly.

I've been doing some "game loop" programming, with and without timers, using timers with Intervals from 1 to 5000 milliseconds, multiple timers, one app, multiple apps, etc. and everyone seems to be getting their fair share of the CPU.

The only time you might run into a problem is when you "drop down a menu" (including a control menu) in the VFP app; in that case, performance may become erratic or the VFP app may "stop" all together until the menu is "rolled back up".

The (VFP 6) DOEVENTS performance bug apparently is not a problem either if it is inside a Timer event.