I can't find it documented anywhere, but I recall the maximum recommended number of active timers being 4. I think this may be a Windows recommendation, rather than being specific to VFP.

>Hi everyone!
>
>I've recently 'inherited' a legacy system and was suprised to discover that the programmer who converted it from 2.6 to VFP has no less than 8 (yes 8!) timers on the main form. The main form has a grid on it and these timers mainly contain code to interact with the grid (i.e. Resize, Refresh, Navigation, Columnsize, etc.). Some of the timers are at the container class level and some are at the form level. They are turned on and off based on different criteria.
>
>My knee jerk reaction is to move the code into one or two timers and use flags and counters to determine if and when code fires, but I was just curious if anyone has this number of timers going at once in their apps and if so what problems can occur?
>
>Our clients are also having a problem with the system locking up at times when other forms are called from this main form. I've tried to track down the reasons but so far haven't been too successful. I changed one form from being created with 'createobject' to just being called with do form 'formname' and this seems to have decreased the problem some but it still is occurring. It seems to be more frequent on newer, faster computers.
>
>Even though the timers on the main form appear to all be off (i.e. interval = 0) when the second form is called, I can't help but wonder if my problem could be related to all these timers being in the main form.
>
>Any help or insight would be greatly appreciated!!