When you issue the CursortoXML() use this:
CursorToXML("curSource","lcXML", 1, 0, 0, "1")
The final parameter creates an inline schema so that XMLtoCursor knows what the column types are.
Laurie
On 21 July 2016 at 11:50, Paul Newton Paul.Newton@pegasus.co.uk wrote:
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]