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:profoxtech-bounces@leafe.com] On Behalf Of Paul Newton Sent: 21 July 2016 11:50 To: profoxtech@leafe.com 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]