I ran across phantom break points - not very often, but it happened. Never did find out what caused them, but leaving vfp and after restart recompiling all usuall fixed it.
>
>The debugger does have some quirks, but what you describe is not one of them, at least in my experience.
>
>Every time I had the debugger consistently fail to stop where I expected it to, the reason was one of these:
>
>2) I had a prg with twice the same procedure/method/function. The last one (i.e. the one last compiled) wins and gets run; if I put a breakpoint in the first one, it won't fire.

not necessarily last one compiled: if same named function is in different prgs, it depends on the order of set procedure to which file...