I test in a different VFP session, using a different foxuser.dbf. Setting breakpoints in my development environment never works. After my test environment is up and running, I go find the code where I want the break to happen. If it is a form I am wanting to debug, which is usually the case, I use a modal dialog to find myself in the form. I then go find my code.
HTH, Tracy On February 27, 2016 10:19:15 AM EST, Alan Bourke <[email protected]> wrote: >The breakpoints have always been a bit hit and miss for me. I always >just stick a SET STEP ON in. > >-- > Alan Bourke > alanpbourke (at) fastmail (dot) fm > >On Sat, 27 Feb 2016, at 09:08 AM, profox wrote: >> Hi Foxgang. >> I think I mentioned this before. Often I want to debug and put a >> breakpoint in. It starts debug screen ok but does not stop at the >> breakpoint. However if earlier I put a set step on, it does. It’s >really >> P’ing me off as it seems hit and miss. I do set resource off in >> config.fpw but I’m not convinced that is the issue. It’s making this >good >> idea into a joke. VFP 9 fully loaded with SP’s. >> I can’t be the only one, can I? >> Al >> >> Allen Pollard >> GSL >> >> >> >> --- StripMime Report -- processed MIME parts --- >> multipart/alternative >> text/plain (text body -- kept) >> text/html >> --- >> [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/[email protected] ** 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.
