>>Has it ever been fixed? Will it ever be fixed? When you double-click a line in the debugger and the red dot does not show up, but the breakpoint is added (as seen in the breakpoint), however it doesn't actually stop on the breakpoint, it's just a little bit irritating. I deleted FOXUSER. I was thinking that had fixed it some in the past. Not this time. What's up with this? This is why I still use SET STEP ON a good bit - I just don't need the hassle of breakpoints not breaking (on a light note, maybe this is better than the problem in VB 5 where you'd clear a breakpoint and it would still keep breaking there <g>).
>
>The only time I've seen a problem with creating a breakpoint in code and having it not stick is when the program hasn't yet been saved. Can you provide reproducible steps for the situation you describe?
>
>Tamar

No, I can't. It has been saved because I always compile to an EXE and run that. You might not have encountered it, but it has been discussed here because others have seen it happen, also.