One more thought on this Michel ... since it seems that you might be working with these people who are providing this WebService for you ... ask them to add additional methods that simply call their existing methods and then do the GetXML() afterwards. IOW:

  [WebMethod]
  public string listEventsForTypeXML(string MyParm)
  {
    DataSet ds = this.listEventsForType(string MyParm);
    return ds.GetXML();
  }

It would *not* be hard for them to do ....

~~Bonnie


>>If you take off the ?wsdl and just go to >http://aspalliance.com/webservices/events.asmx, you'll see a description of the methods you can call. They explicitely state that they return DataSets. You'll need to parse these with the XMLDOM. It would be nice if they had methods that instead of:
>>

>> return MyDataSet;
>>

>>
>>they had methods that did:
>>

>> return MyDataSet.GetXML();
>>

>>
>>But, since they don't, look at what you get back from the WebService:
>>

>> oXML = o.CallTheMethod()
>> oXML.
>>

>>
>>What you'll see (probably, assuming that they are indeed returning a DataSet) is the items that belong to certain objects in the DOM, the IXMLNodeList. Check out:
>>

>>?oXML.item(0).parentNode.xml
>>

>>
>>Anyway, you can mess around with this and parse it yourself, or as I mentioned earlier, wwXML will handle it as well.
>
>Are VFP developers the only ones to use such an advance approach like CursorToXML() and XMLToCursor() instead of having to scroll down each node and do this primitive manipulation? :)
>
>Thanks for the help on this, I'll have to use that approach if I wish to use that data.