Hi,

>>
The company I am dealing with have said that the supported methods of access are using Java SOAP Client or .NET Client and have supplied me with sample code for these - I'll email these to you. They have said that they have successfully used a VB Client but I am still trying to get hold of this.
>>

Hi, got the email. Unlike Geraint I do not see a problem with the webservice parameters - they are just enumerations not objects. IAC, AFAIK if VFP receives a complex type from a web service it just treats it as an XML doc.
That said using a .NET wrapper is always an option.

I did notice though that the sample .NET client code was passing credentials to the web service and you were not doing this in VFP. Do you have a username/password ? If so prefix the URL in SetupClient() with this information e.g:
http://domain%5cusername:password@url

If that gets you any farther you will also need to set the "AuthUser" and "AuthPassword" connector properties on the client before calling any methods.

Just to be sure : the company hosting the web service have definitely tested this from other external locations over VPN ?

>>
I apologise for taking up your time and I hope you're not getting fed up of me picking your brains!!!
>>
No a problem (but I'm afraid I usually only get to check UT once a day..)
Just wish we were making more progress :-(

Regards,
Viv