Breakpoints you set in the code window are not updated correctly if you add/remove code before the location where the breakpoint is set. That's why you get it seemingly stopping at places where you don't actually have a breakpoint set, or not stopping where you think you have a breakpoint set.
Fred
On Thu, Jan 14, 2016 at 3:14 AM, Allen Pollard profox@gatwicksoftware.com wrote:
Hi gang I seem to be having problems with VFP9 (fully updated) debug. I think this has been a problem before but at the moment I find it often does not stop on a break point and I have to revert to set step on. Or the other way, it stops at placed I have no break point on. I have one debug I'm checking now and it stops twice during a scan which is fairly large and bloody annoying as I have to clear the break points to get it going again and lose the break point I want. Seems this time saver is taking more time than without. Does anyone else have this issue? Set moan off Al
[excessive quoting removed by server]