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 <[email protected]> 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] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJCBksqCsU-s+P+5=d2gg6-ahp558du-seywxojuw3gblhw...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
