>Thanks again, Viv! So, I can just httppost the SOAP xml basically, it seems (as long as I have the headers set correctly). I guess using SOAP with vfp's ffc classes is only good when non-complex object types are involved (ie. passing/returning objects is not doable)? Is that a fair statement? Many thanks again. If anyone else can offer some help too, I would surely appreciate it. I'm just surprised that VFP's ffc classes have such limitations with SOAP after all the talk about using SOAP with VFP. Just one more question, should I be using the SOAP 1.1 or 1.2 examples shown in the method samples at:
http://www.triphomes.com/webservices/wvrgroupservice.asmxVFP and MSSOAP were never a good fit for anything more then very simple webservices. IAC, MSSOAP is pretty much out-of-date and MS are not producing a newer version. If what you are doing here is a one-off requirement then XMLHTTP should be OK. However, if you expect to be dealing with Wewbservices a lot you might consider using .NET to communicate with the WS and pass results to VFP.
In VFP I normally create a class for all communication with a specific website using seperate methods for each webservice used. The method only populates the service specific elements then calls a common method to add the SOAP wrapper elements and dispatch the XML. I usually prefer handling the response by accessing the .responseXML property but for simple cases parsing .responseText is easier.
I think it's SOAP 1.2 but don't think it's essential,
HTH,
Viv
