I have encountered methods in the past that kept breaking into Trace mode without displaying a breakpoint. For me, the breakpoint handling in 4D reached its lowest point with v17. I saw methods that would continue to drop into Trace mode with no breakpoints showing. The only solution was - create a new method - copy in the code from the problem record - delete problem method - rename the new method (to the old method)
Also, v17 had a severely bad habit of ignoring breakpoints after a short time tracing code during development. I never did figure out what triggered it (modifying code in a method currently being traced?). The only solution to get breakpoints working again was to restart 4D. Cheers, Keith PS If anyone knows what the trigger was or how to prevent 4D from ignoring breakpoints (using v17) I’d love to know as I’m doing a short stint of v17 work and am having to wrestle with this problem again. ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
