>Hi Viv
>
>Thanks for the reply.
>In your reply you say
>
>"I assume you are referring to the MSSOAP dll (which was the simplest way for a VFP client to access web services). This is no longer supported but SOAP itself is not going away. If you intend developing the client side using VFP then the simplest solution would be to use .NET wrappers to access the webservices"
>
>Can you elaborate on this ? or point me to some example.
>
>My client & server will be exchanging XML cursors over the web, both client and server will be in VPF.
>I have some docs on how to pubish VFP COM with ASMX and I have some sample to use it on the client side.
>I do not know how to convert the data to XML and how to send it using those tools.

The link to Rick's white paper that Michael provided should give all the detail you need.

But if you simply want to pass VFP cursors then you could just use CURSORTOXML() to create the XML, a net wrapper to pass this as a string over the web, then XMLTOCURSOR() in VFP on the receiving end. In this case the .NET asmx code on the server would be trivial. Something like:

[WebMethod]
public string GetOrder(int OrderId)
{
     return VfpCom.GetOrder(OrderId)  // Where the VFP com server method would return the relevant CURSORTOXML
}

If you want to pass objects then .NET will serialize/deserialize these to XML transparently - you just don't worry about it.

But, as mentioned in Rick's paper, note the potential threading problems when using a VFP com server with asmx pages.
HTH,
Viv