maybe you could run METHOD GET CODE on all methods just to see if all methods are accessible. if it really comes down to that, I guess you could run METHOD SET CODE on all methods too.
or, you could trash (helps if the trash is empty) some methods to exclude them from the compiler. compilation would likely fail due to missing methods, but at least it should be able to complete its task. then you can restore those methods you hid in the trash. > 2017/08/21 9:21、Randy Engle via 4D_Tech <4d_tech@lists.4d.com> のメール： > Any great ideas about how to find this elusive error? ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
