>
This.Parent.Text1.Value = oWSConsignee.SelectAllCustomer
I previously replied to this on the MS newsgroup. You have to use some extra code to get to the XML string.
loNodeList = oWSConsignee.SelectAllCustomer()
lcXML = loNodeList.Parent.XML
>A Web service is suppose to return XML, I mean text (SOAP/XML).
Not necessarily. IN this case it returns a DataSet Object which the SOAP toolkit returns as a schemad XML response, which is different from an XML string. Anything schemad in this fashion is retured as an XML nodeList and you have to use the parent node which is the root of the XML result to do what you need.
>An it's impossible to look into this object in Debug mode (Watch window)?
Use Intellisense and you do get the properties for that object (in this case) as an XML Node list.
>A moderator from Microsoft explained that MS Visual Foxpro 7 is the first .NET product that they deployed with the possibility to create and consume Web Services. And he said MS Visual Foxpro 7 is an active part of .NET strategy.
>
>Today, All those News groups are no longer active????
Things change. That post is probably a year old.
Visual FoxPro is not part of .NET, but you can interact just fine with .NET using interop services and Web Services.
>We have no documentation, no news groups and no books talking about that!
Lots of people talking about that, but that was months ago. You can't expect to walk in on generic newsgroups and find the answers you're look for right then and there. Ask an intelligent question and you shall get an intelligent answer <g>...
