>>Don't use STEP ON. Go to the line of code, right-click and click on SET BREAKPOINT. You can also use the ASSERT command [see VFP help and use with SET ASSERTS ON command].
>>
>>
>
>That's all fine and good, but sometimes breakpoints seem to get ignored and will not trigger in a compiled .EXE - or am I missing something?

Before you compile, go to the VFP menu and click on Project, then on Project Info. Make sure Debug Info is checked on the Project tab. Then as long as the debugger is open, breakpoints will be honored when hit.

Also, if you use the debugger to start an APP, EXE, PRG or form, you can step each line of code from the beginning. At that point you can scroll down to any line and double click next to it to add a new breakpoint. If a form, you can use the combo boxes to change to a different [instanciated] control and method and set a breakpoint.

You can also drag and drop objects, variables, properties into the watch window from the code in the trace window. You can double-click in the left grey column next to anything in the watch window to set a breakpoint. This type of breakpoint will break when the value of that object changes.

Hovering the mouse in the trace window over a property or anything else with a value will display the current value of that object as a tool tip.