Hi Robert, You worry too much. Orphaned methods are nothing to lose sleep over. It’s just a 4D bug in how it handles deleting methods connected to objects. It does a less than perfect job of handling this. Sometimes it does it right, sometimes it screws up. Been this way for years in untold number of 4D versions.
My philosophy is that when I see references to orphaned methods I simply delete them and move on. I don’t even give it a second thought. There is a line from an old Chicago song “you learn to live with it... but I don’t want to” that really sums it up for me. :) Tim Sent from my iPad On Nov 17, 2018, at 2:00 PM, Robert wrote: > Actually I was using build 229490 but now I’m using the most recent (229707) > with the same behavior as previously reported. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
