Here's an article: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnfoxgen7/html/vfpws.asp
Yes, you need IIS for a vfp web service. You need to include the vfp8t.dll runtime, language resource dll, your vfp mtdll(register it on the PC), your vfp mtdll's tlb and vbr files, and the vc++7 runtime. You can automate all of this with an Installshield project.
Always compile to a vfp mtdll, if there's any chance more than one person at a time will be accessing the web service. Always use the Session class. Always use COMRETURNERROR. I would use the ASP listener since it's built in to the majority of MS OSs (or use an asp.net listener).

>I have a client who is running a website which we think would benefit from calling a complex function that I have written in VFP. The function must be able to accept 6 parameters and returns 5 output values. I am therefore thinking of providing the function as a web-service that will will accept the input parameters and output values as XML strings. The service is to be hosted on the client's web-server machine, which is not connected to the development machine.
>
>What files will I have to send to my client? From what I have read so far I guess they will need at least the following...
>Web-service .dll file
>VFP8 runtime files
>WSDL/WSML files created by publishing wizard
>Any others?
>
>The function will require access to some small .dbf tables. Rather than supply these as separate files, is it ok to included them in the .dll (as I would for an .exe running on a network)?
>
>Apart from the SOAP toolkit, what else will my client need to install the service? Must the web-server be running IIS, or could it be a non-Microsoft server such as Apache?
>
>Any other help would be appreciated. Is a web-service the best way to go? Are the FFC web service foundation classes worth looking at? Are there any good articles/papers out there that could take me through the process?
>
>Many thanks,
>Alan Harris-Reid