>SNIP
>>>"Timers fire when the menu is dropped down. They didn't in VFP 3.0. Timers fire in toolbars. Timers fire when a form is being dragged around. Timers fire when another application window is resized, or when Fox's window is resized. Timers fire when your application displays a message box. Awesome!"
>>
>>Thanks for the info. I already was wondering why I was getting this work and others not. This piece of documentation seems to confirm my believes.
>>
>Walter and Steve,
>
>Now I don't know what the story really is...
>
>Yesterday, finding Whil H.'s explanation, I also ran the test code he included. That code essentially issued a MessageBox() that stopped under specific conditions, aimed at proving that the timer 'keeps on ticking' (does not fire) during the wait on the MessageBox.
>
>It acted as Whil described in that, leaving the WAIT in effect for some time resulted in no additional MessageBoxes and no update to the counter he was displaying to make the timer fires evident. There was also no sudden burst of subsequent messageboxes, even after letting one sit for over 5 minutes while I made tea. I'm going to have to go look at that code.
>
>But at this point I guess it could be that the "firings" stack up internally, being delivered to the application in rapid succession once the WAIT is ended. Or it could be that they do not fire at all during the WAIT, as Whil suggests.
>
>This was done with VFP7 (not 3 < s >)
>JimN

Jim,

I know you don't do you work in VFP3 *grin*; I just figured you have read that as a potential GOTCHA in the book and were throwing in your Canadian 2 cents <g>.

I sounds like you're saying it doesn't fire when a WAIT is in effect. The original quote you provided from the book warned against the menu being active. If you post some test code I would be interested in trying it out (I don't have the Fundamentals book).