Thanks Rick

I think on reflection I will go down the net interop route.

Nick Mason


>>2. Convert the web service to .net and call the foxpro com components. (Is that called interop ?)
>
>I would recommend going this route anyway. The SOAP Toolkit is pretty limited in what it can do (although it works for simple things like passing strings back and forth), but more importantly it doesn't support the latest protocols and won't be enhanced.
>
>So going the .NET route is a better choice for going forward. But it's more work as you manually have to create the Web Service front end for your VFP COM component - which may actually be a good thing because it forces you to explicitly design your Web Service interface.
>
>
>As to getting the SOAP Toolkit to work I think the most common problems are:
>
>Security:
>Make sure the various extensions installed by the SOAP toolkit are allowed to be executed in IIS 6.
>
>ISAPI Installation Failure:
>The ISAPI connector doesn't install correctly when the SOAP Toolkit is installed and you have to manaully install it. Search for it online you should find a number of articles that discuss this issue.
>
>As an alternative you can also use the ASP listener which does install correctly. Again make sure that ASP is enabled on IIS 6.
>
>
>
>
>
>+++ Rick ---
>
>
>>Hi
>>
>>I've created a foxpro web service using mssoap which runs ok on a Windows 2000 box. The problem is the service now need to move to a server 2003 box.
>>I can't get it to work on the Server 2003 box.
>>The service passes data to and from via xmltocursor and cursortoxml.
>>
>>I'm in two minds about this.
>>
>>1. is to solve the problem on the server2003 box(but I haven't a clue what is the problem and see that MSSOAP isn't supported anymore or at least not for much longer)
>>
>>2. Convert the web service to .net and call the foxpro com components. (Is that called interop ?)
>>
>>I'd welcome some opinions.
>>
>>Thanks
>>
>>
>>
>>Nick Mason