>>She no workee. I have the debugger open and can see the breakpoint listed, but the EXE blew past it like a freight train.
>
>Then try this. Where you want to stop execution, put the following command:
>
>ASSERT 1=2
>
>Before you run the EXE, type the following in the Command Window:
>
>SET ASSERTS ON
>
>When it hits the ASSERT 1=2 line, you will get a message box where you can start stepping through the code. By default, at runtime, SET ASSERTS is OFF so all ASSERT command lines are ignored.
That tactic works, thanks.
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
