Hey Tim, Thank you for the references. You are always so prompt with spot on links like that.
I get the thinking about runtime errors - but in the absence of a workable way to test the validity of a JSON string in compiled mode it seems a good place for an actual method to do this. Or writing in something in the JSON Parse methods that throw that error as something that can be trapped. Not to re hash this discussion but it sure seems like a real problem. Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* On Wed, Jan 31, 2018 at 4:09 PM, Timothy Penner via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Hi Kirk, > > Have you seen these tech tips? > > Tech Tip: Range checking errors are not caught ON ERR CALL in compiled mode > http://kb.4d.com/assetid=77848 > > Tech Tip: Consider disabling "Interact with the desktop" when running 4D > Server as a Service > http://kb.4d.com/assetid=77847 > > We also have this tech tip - but I suppose it doesn't work in compiled > mode... > > Tech Tip: How to check if TEXT is an OBJECT / JSON > http://kb.4d.com/assetid=77555 > > -Tim > > > > ********************************************************************** > 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 > ********************************************************************** > ********************************************************************** 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 **********************************************************************
