Tim,

>There is a method on the adapter which returns the XML as a string. This can then be passed to the Microsoft XML DOM to create a standard XML Document from within VFP. This DOM, as i understand it, is used across the board in Microsoft's XML functionality. This was what lead me down the path of passing DOM object around as the base coding is all the same provided it's all done on the Windows Platform<

I might be wrong about this, but I don't believe that an XML DOM object is the same as .NET's DataSet object and that's why you had a problem doing it that way. So, yeah, just stop at the "XML as a string" stage of the game and just pass that to your Web Service method.

>Once again, thanks for your time in helping me out here Bonnie.<

No problem, Tim. Glad to help. =)

~~Bonnie


>It's all to do with the XMLAdapter class, new to VFP8. You can read in cursors and have all of them contained within this object. Similar to the .NET dataset in concept, but with very basic functionality. This isn't where you get the DataSet object from however.
>
>There is a method on the adapter which returns the XML as a string. This can then be passed to the Microsoft XML DOM to create a standard XML Document from within VFP. This DOM, as i understand it, is used across the board in Microsoft's XML functionality. This was what lead me down the path of passing DOM object around as the base coding is all the same provided it's all done on the Windows Platform
>
>But you're right, if my method accepted an XML string, it would be more accessible for other languages. And it's as long as it's short in reality. I convert an XML string to the DOM from within VFP, or I convert it from within .NET. I imagine the .NET route would be slightly quicker in processing, and probably more optimized than plain VFP
>
>Once again, thanks for your time in helping me out here Bonnie.
>
>cheers
>
>Tim