>>I have set breakpoints in my code and have even inserted SET STEP ON.
>>
>>The debugger can be open, but the debugger does not engage.
>>
>>????????
>
>Sounds to me like you're not running the code you think you are.
>
>Tamar

Perhaps he isn't running the code he thinks he is, however there is very definitely a bug in VFP that causes this. I believe CLEAR DEBUG, as Naomi has suggested, will often fix it or the other solution seems to be to delete the FoxUser table, or the other solution is "just wait awhile." I have this happen to me and so I tend to still use SET STEP ON more than I care to because you can't tell when this bug will rear its ugly head (and sometimes even SET STEP ON is ignored). I also have noticed that I will double-click to add a breakpoint and will not get the red dot, yet the "Clear Breakpoints" button becomes enabled (it's only enabled when there is one or more breakpoint to clear). I can open the breakpoints dialog and see the breakpoint, but VFP will not stop on it. Sometimes you can get fooled on a multiline command when the last line is below the bottom of the window, because, as you know, the breakpoint dot goes by the last line and you just don't see it, because it's below the bottom of the window. However, I have seen this problem occur many times on a single line command that has many other lines below it. No red dot, VFP does not stop on the line. But later it may decide on its own to start working properly. Of course, I may have exited and restarted VFP one or more times, but I haven't done anything other than that. It just decides to start working.