There are no work-arounds for runtime errors. 4D throws up an error dialog and allows the end user to decide what to do, even if executing on 4D Server or in a web process.
See feature request and discussion here: http://forums.4d.com/Post/EN/17994245/1/19128922 John DeSoi, Ph.D. > On Feb 1, 2018, at 10:09 AM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > So in a compiled app I don't see how I get to the point of using tools like > Ob is defined or OK because I don't get past the runtime parsing error. And > I'm not able to readily determine where the offending string comes from > because there's no way to log the error. (This particular method is reading > JSON data coming from outside 4D.) > > I hope I've missed something along the way because I'm not coming up with > any good workarounds. ********************************************************************** 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 **********************************************************************
