Charles,

You can check out the West Wind WebService Proxy Generator which creates wrapper proxies for you in .NET. It creates a .NET assembly for the Web Service and a FoxPro proxy using wwDotnetBridge that calls the .NET proxy along with the wwDotnetBridge helpers that facilitate access to arrays and .NET types not easily supported in native COM.

It'll work with most Soap 1.x Web Services but does not support WS-* Web Services (those have to be hand accessed).

West Wind Web Service Proxy Generator:
http://www.west-wind.com/wsdlgenerator/

This tends to be a better solution than the SOAP Toolkit because it uses the more robust .NET Web Service tooling that isn't deprecated. But - the SOAP Toolkit should work. I'm not sure what would lock MSXML4 unless for some reason msxml4 is not installed or not patched to the latest versions.

Hope this helps,

+++ Rick ---

>Trying to help a friend connect to a web service. Windows 7 64 bit , VFP 9.0
>
>Any attempt to register the WSDL URL for known web services results in an error in addfoxcode() that says permission denied on msxml4.dll
>
>VFP is set to always run as admin and he is logged in on his admin account.
>
>He has SOAP 3.0+ toolkit installed, but I'm not sure if .NET has superceded that.
>
>I am a VFP / web idiot so any suggestions would be appreciated. Googling the msXML4.dll thing has a very high noise to signal ratio.
>
>TIA
>
>(is there any magic in WW stuff that might facilitate this?)