I had been hoping to avoid adding another layer on top of things especially since it seemed so easy on my XP box, but it does look like wrapping my VFP COM objects in a VS Web service *should* work. Publishing a VS2005 web service that internally is using my VFP objects should be easier (f course, I've only tested creating VS2005 web services on my developer box, and only using VS2005 code).

I'm going to give that a try tomorrow and see if there is hope. I really hope so - we have a lot of VFP code that can be reused.

>Since SOAP Toolkit is not going to work on the Windows 2003 Server, another option is to create the Web Service in .NET, but leverage your existing VFP code by making it COM and use Interop in the WebService to access it. I think there's a few headaches with Interop, but not having used it at all myself, I couldn't tell you what they may be.
>
>You might want to check out Rick's white paper on the subject:
>
>http://www.west-wind.com/presentations/VFPDOTNETiNTEROP/VFPDOTNETINTEROP.HTM
>
>
>~~Bonnie