Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Runaway Debugger!
Message
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Environment versions
Visual FoxPro:
VFP 8 SP1
OS:
Windows XP SP2
Network:
Windows 2000 Server
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01025955
Message ID:
01025957
Views:
13
Ignore the ORIGINAL question.

I was running the EXE.......... sigh, not the source code.

But, the controls in the debugger flicker and act like they are still being fired upon by the Timer(s). There is another timer that updates a textbox with the DateTime. I tried to disable that one in the code too.
Is there something I am overlooking to shut down the timers so the code can be traced?

Thanks!

>Hi Gurus...
>
>Question
>
>If you want to bring up the DEBUGGER in your code, a simple SET STEP ON will do.
>
>But if the code happens to be the TIMER code in a TIMER object, like this...
>
>
>TIMER.TIMER
>
>this.Enabled = .f.
>
>ACTIVATE SCREEN
>?
>? "BEFORE STEP AND ECHO"
>?
>SET STEP ON
>SET ECHO ON
>
>Local lnArea, lcday, lctime, lbRefresh, ldCurrentDate, ldDialDate, llDoSkippedDial
>lnArea = Select(0)
>
>
>The Debug Window never comes up.... it keeps firing and running the code, ignoring the SET STEP ON.
>
>How do you get it to observe the SET STEP ON, in this case, for debugging?
>
>Thanks!
Tommy Tillman A+ NetWork+ MCP
Previous
Reply
Map
View

Click here to load this message in the networking platform