Hi Francois,
How about having your oWSConsignee return ds.GetXML() ... this would then return a true XML string and you can then use XMLToCursor() without a problem.
~~Bonnie
>Hi Nesimi,
>
>I have the same problem an I'm searching a solution since a couples of days. It's hard to find documentation on that.
>
>I can access my Web Service and make a call like that:
>
>
This.Parent.Text1.Value = oWSConsignee.SelectAllCustomer
>
>A Web service is suppose to return XML, I mean text (SOAP/XML).
>
>But in foxpro it returns an object.....? It's Big big problem...
>
>An it's impossible to look into this object in Debug mode (Watch window)?
>
>I'm sorry Nesimi but I'm going to use your Thread to highlight the importance to this case.
>
>Here an exemple of how hard it is to find informations about VFP working with .NET:
>
Last Week I say 5 or 6 news groups named like :
> microsoft.dotnet.vfp.something... and I subscribe to them.
>
>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????
>
>We have no documentation, no news groups and no books talking about that!
>
>ALONE IN THE DARK.....>
>
>Please, if someone from Microsoft read this, we realy need help...
>
>We need to access with VFP7 to Web services create with VFP7 or ASP.NET. And we need to parse the data return by those Web Services to a Foxpro Cursor.
>Otherwise I think, VFP7 is no longer an active part of .NET strategy.
>
>Sorry for this, but I need answers on what front-end I'm going to use in the futur,
>
>Thanks,
>
>François
