4D Tech mailing list wrote > Yeah, if 4D isn't working, try NTK. In either case, if you can get at the > value as raw text then you'll be able to find text --> 64-bit conversion > code. The question in 4D at that point is how to store it. I know it's a > field type, but can you touch it with anything other than SQL?
Unfortunately, 4D seems to munge the value immediately within the object when the HTTP response is returned in an object. And the same happens when I use NTK's JSON Get Number. So unfortunately I'm a little stuck. I've asked Rob if he can figure out how to return the value in a string. -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 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:[email protected] **********************************************************************
