LOL


>Yikes!! Subtle ain't the word for it! <g>
>
>I see what you mean. My bad.
>
>>Roger,
>>
>>Nope, that's where you're wrong. There's a subtle difference between a WebService that returns
>>
>>

return myDS;

>>and one that returns
>>

return myDS.GetXML();

>>
>>The difference is that returning the DataSet itself returns an object and if one attempts to use it from any other client other than a .NET client, one needs to use the XMLDOM to parse it out correctly. Thinking of it in these terms, getting a DataSet from a WebService and then trying to use it in VFP with XMLTOCURSOR(), you would not be able to do it. You have to go through all that crap of using the XMLDOM to parse it out correctly before you can get the data out of it. (Or, as I'm sure Rick may jump in here and tell everyone <g>) ... you can use Rick's wwXML for easier parsing. Regardless, the point is that you can't utilize that XML without doing extra stuff to it.
>>
>>If, however, the WebService returned myDS.GetXML() then that is a pure XML string that can be utilized as is from any other client. VFP can simply do a XMLTOCURSOR() with no problems.
>>
>>And it's not just VFP that would have problems with the straight DataSet ... other clients will too. It's not a standard way to return data from a WebService.
>>
>>
>>~~Bonnie
>>
>>