go into Tools/Breakpoints (or hit CTRL-B) and look at the listing. I'm betting y'all added the '?Phantom ' line after you set the breakpoint - so it's breaking on the line number that you set the break at. I've run into this behavior with VFP8 even after I've cleared the 'red dot' in the debugger.


>Hello everyone:
>
> Sometimes, vfp debugger stops at some invisible breakpoints.
>
> There is a test program from Mr. Leonid Lepin (or Mr. meligo):
>
>

>     *PROC testbreakpoint
>
>     SET STEP OFF
>     SET ECHO OFF
>     SET DEBUG OFF
>     SET ESCAPE OFF
>     SET TALK OFF
>     SET SAFETY OFF
>
>     _SCREEN.VISIBLE=.T.
>     _SCREEN.WINDOWSTATE=2
>
>     ? 'Phantom BreakPoint'
>     INSERT INTO tttt (f0,f1,f2,f3,f4,f5) VALUES (CHRTRAN(somestring,'\','/'),1,2,3,4,5)
>
>     RETURN
>
>     * END OF PROC TESTBREAKPOINT.
>

>
> We can set a breakpoint at the line:
> INSERT INTO tttt (f0,f1,f2,f3,f4,f5) VALUES (CHRTRAN(somestring,'\','/'),1,2,3,4,5)
>
> But when we run the program, the debugger stops at the line:
> ? 'Phantom BreakPoint'
>
>
>More details please refer to:
>
>VFP 9.0 FIX - INVISIBLE BREAKPOINT
>http://www.baiyujia.com/vfpdocuments/default.asp
>
>source code download:
>http://www.baiyujia.com/f_download.asp