Yes, it helps a lot, but unfortunately I think there is a problem in Sourse of webservice :) And it probably was generated by ASP.NET ...

I can give only two possible solutions:
- may be it make sence to insatll on your (client) computer fresh XML parsel from Microsoft (they distribute it as a whole package)... I have version 4.0
- I do not know exactly in ffc\_webservices.vcx clsss :( May be problem there...


>I think I might be confusing you. I haven't got any code.
>
>The web service I am trying to link to is remote and has nothing to do me. I have been given a an ip address and have used VPN to establish a link between my pc and their server. When this link is active I can go on to Internet Explorer and enter the url followed by ?wsdl and it displays all the xml code.
>
>I thought I should be able to use the IntelliSense tool to register the Web Service in Fox when this VPN link is active but that is when I get the error parsing the XML code.
>
>I have used this method and never had the need to code any DEFINE/ENDDEFINE statments to declare the web service. All I have done before is register the webservice in intellisense and then when I declare a variable oWS the intellisense prompts me with a list that contains my registered web services and when I choose one, Foxpro automatically generates the following code
>
>I type in
>LOCAL ows as MyWebService
>
>and Foxpro automatically generates the following
>loWS = NEWOBJECT("Wsclient",HOME()+"ffc\_webservices.vcx")
>loWS.cWSName = "MyWebService"
>ows = loWS.SetupClient("http://99.999.99.99/POSService/POSService.asmx?wsdl", "POSService", "POSServiceSoap")
>
>
>I don't fully understand it but I thought the wizard linked through to the web service and interpretted the xml and translated it into an object list ready to be used in Fox.
>
>Don't know if this helps or not??