Hi Dar - yeah, I wondered about that but the problem elements contain text or a mix of text and numbers so they really should be ok to start with. The weird thing is that I have two apps, which are essentially versions of the same project. Both use similar data files as input and both use jsonExport() to output. One throws a wobbly on certain elements and the other doesn’t. It’s got me.
Terry... On 14/06/2016 11:32 am, "use-livecode on behalf of Dar Scott" <use-livecode-boun...@lists.runrev.com on behalf of d...@swcp.com> wrote: > >> On Jun 13, 2016, at 6:34 PM, Terry Judd <terry.j...@unimelb.edu.au> >>wrote: >> >> If I go through all of the array elements in turn it is possible to >> identify the problem ones and I can Œfix¹ each of them by doing this... >> >> put empty after tData[<tElement>] >> >> ...after which jsonExport() runs just fine. > >Maybe I'm just stating the obvious--since you have this solution, you >probably know. But just in case... > >This will turn a number into a string. it does it using the numberFormat >at the time and place of the 'put empty after'. > >I'm guessing jsonExport() is gagging on the result of arithmetic. > >Dar > > >_______________________________________________ >use-livecode mailing list >use-livecode@lists.runrev.com >Please visit this url to subscribe, unsubscribe and manage your >subscription preferences: >http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
