>Jim,
>
>>You are right. I am wrong.
>
>Thanks, I was getting confused.
>
>>In any case, looking further into this, it looks like it is VFP INTERNAL things that can interfere, NOT external processes. From "The Fundamentals..." by Whil Hentzen:
>>"The timer does not process when a menu bar, pull-down menu or popup menu is open. For example, you can cause something to happen when the timer event is fired, such as a WAIT WINDOW command or a message dialog, and the Timer control keeps ticking." (by this I think he means it does not fire, even though the interval may lapse several times during the specific VFP process)
>
>It seems that this also is not correct. In my framework I've got a timer to display statusbar messages in a custom activeX status bar. Since it perfectly displays messages of the open pulldown menu, this can't be the case. I believe this was changed from VFP 5 to VFP 6, but I'm not certain. Though not checked, I think that the only instance VFP is blocking timer events is by:
>
>1. Program running. IOW no wait states to process the timer event, unless a DOEVENTS() is processed.
>2. Explicit modal dialogs, like WAIT WINDOW, MESSAGEBOX and the ERROR dialog.
>
>Cheers,
>
>Walter,

If I "pull" down a Control Menu when my VFP App is running a Timer loop, it "stops". Only when the Control Menu is closed does the App start up again.

With ActiveX, you're adding something else to the mix.