Thanks for your reply. All the loWSHandler errors are either false or blank so that seems okay. I see you also relied to my earlier thread about the duplicate names.

I don't know a lot about web services/xml but I did think that Fox wouldn't like the duplicate names so contacted the company who then loaded a bug fix at their end, regenerated the wsdl and now I seem to be able to link through okay with no errors but it doesn't create the final object successfully.

I have connected to a web service before but did it by supplying a URL followed by .asmx?wsdl. I’m guessing this uses something at their end that generates the WSDL file and this is then returned to Foxpro and is converted to an object by Foxpro and that object has all the methods specified in the WSDL.

When I connect to this system (access to the system can only be done via VPN), I cannot do it in the same way. I specify the URL followed by ?wsdl so I think this must return some pregenerated WSDL file that has been generated at their end. From what I can gather, I think they use sometihng called AXIS so I am assuming that this has already generated the WSDL and I just pick it up and for some reason it’s not compatible with Foxpro so it’s not interpreting it correctly. I have tried entering the URL followed by .asmx?wsdl and I get the message ‘AXIS error. Could not generate WSDL. There is no SOAP at this location’.

Not really sure where to go from here. Have you any ideas?

TIA

Sue