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.

~~Bonnie


>>That doesn't look like something that XMLTOCURSOR() would be able to handle. How was that XML generated? I'm no XML expert, but at first glance it doesn't appear to be well-formed XML.
>
>This is from this page:
>
>http://aspalliance.com/webservices/events.asmx?wsdl
>
>That's the definition of a Web Service they provide. We already told them what we need to do exactly in order to benefit of those methods. They are all using the schema approach. We are awaiting instructions before consuming their Web Service.
>
>This was generated from the .Net environment. Do you see anything we could do to succeed? The only way we can make it work is from the browser:
>
>http://aspalliance.com/webservices/events.asmx/listEventsForType?BeginDate=6%2F22%2F02&EndDate=7%2F22%2F02&EventType=9