Hi Sergey,

I agree that SOAP 3.0 is probably not the right tool to publish Web Services at this point. For VFP servers probably the best way to do this is to use ASP.NET -> VFP COM, but the SOAP Toolkit definitely works and while it has its quirks it is at the moment at least the most automated solution that comes out of the box.

It does work, but server configuration is critical and unfortunately when something does go wrong the ASP based SOAP server portion (or the IASPI one for that matter) leave you no clear answers where to go looking. It does work though if you follow the instructions in the configuration guide.

Part of Win2003 too is that it's locked down by default and you have to unlock the Web Server first (enabling extensions, especially for any custom ISAPI extensions) - this will hapen regardless of whcih tool you use.

Regards,

+++ Rick ---




>Hi Rick,
>
>I have a personal experience :(
>
>I did spend four days for trying to do it, but could not... And I found thread on UT, that somebody had the same problem and could not find easy solution.
>Furthermore - Ken Levy did not recommend use SOAP 3.0 on a server side for future development.
>
>So, I took your very useful article (about ASP.NET WS -> VFP) and created server side on VS.NET (VB.NET) but on a client side I am still using SOAP 3.0 + VFP 9.0 (Win XP)...
>
>May be I have missed something?
>
>
>>>Unfortunately, SOAP 3.0 does not work on Windows Server 2003 :( as data source...
>>
>>Uh, I'm afraid this is not correct. Both server and client implementations work just fine with SOAP 3.0. Where did you hear this from?
>>
>>+++ Rick ---