Michel,

Good for you ...they actually listened to your suggestion and changed their WebService to return DataSet.WriteXML() instead of the DataSet?!? See, it pays to gripe about things sometimes, doesn't it? <g>


~~Bonnie



>>Developers should avoid thinking that a DataSet object is an XML document or string since it not. An XML document must be a string which adheres to the W3C rules of an XML document with proper headers, elements, structure, etc. An XML document object is an object which has been created based on an XML string, file, URL source, etc. An XML document may be based on a DOM (W3C document object model for XML), a custom XML API interface, .NET classes found in system.xml, etc. Just think of a DataSet object as something that can be created from XML or exported to XML easily and quickly. VFP 7.0 is not compatible with .NET DataSet objects directly so XML strings are required for interop, as would be the case for many COM or external applications interfacing via XML Web services COM/.NET interop.
>
>To add more to this, following a recent thread, I proposed the Web Service provider of a specific .Net Web Service to return DataSet.WriteXML() instead of DataSet. This was then making it standard and I was able to use XMLTOCURSOR() ok. The previous approach was also making their Web Service less usable for non .Net environments.