Another way to get around the issue without relying on the schema is to append the data to an existing pre-defined cursor, like this:
Local lcXML lcXML = "<VFPData><cursource><a>0</a><b>1</b><c>2</c></cursource></VFPData>" Create Cursor curTest(a N(1), b N(1), c N(1)) XMLToCursor(lcXML, "curTest", 8192) Browse Paul Newton -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Paul Newton Sent: 21 July 2016 11:50 To: [email protected] Subject: XMLToCursor converting numeric values to logical fields Hi all I came across some unusual behaviour with XMLToCursor which the following code clearly demonstrates: Local lcXML Create Cursor curSource (A N(1), B N(1), C N(1)) Insert Into curSource Values(0,1,2) CursorToXML("curSource","lcXML") Browse Nowait XMLToCursor(lcXML,"curTarget") Browse Nowait lcXML looks like this: <?xml version = "1.0" encoding="Windows-1252" standalone="yes"?> <VFPData> <cursource> <a>0</a> <b>1</b> <c>2</c> </cursource> </VFPData> In curTarget fields A and B are logical. Can anybody throw any light on this, particularly how the XML should be constructed so as to ensure that fields A and B are created as type numeric? Many thanks Paul Newton [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
