>>>I can not recall, but I believe there is a SYS() function that can be placed in the Watch window that will stifle the timer event.
>>Sys(2030) maybe?
>
>"Starting with Visual FoxPro 7, whenever user code directly runs a system component, such as _GENMENU or _BROWSER, certain debugging features (profiling, dohistory, breakpoints, and single step) are disabled. SYS(2030, 1) enables you to run debugger on this type of user code by disabling the default behavior, then re-enabling the behavior after debugging by issuing SYS(2030, 0). "
>
>Not sure whether this applies to timers.

SYS(2030) is off by default. You have to turn it on to be able to debug Xbase tools. I don't think it has anything to do with timer events.

However, in VFP's Tools | Options dialog, on the Debug page, there's a checkbox labelled "Display Timer Events." Help says:

Choose this option if you want Timer Control timer events displayed in the Trace Window when their interval value is reached. If you clear this option, the timer event still occurs, but is not displayed; it is treated as if you had specified Step Over for that event.

With this check box cleared, Visual FoxPro filters timer events even when you are stepping through a timer event currently.


Tamar