>I installed from VFP 7's CD but my machine may be screwy - it's working on my laptop but not on my main Win XP machine.

I had the similar problem. In my case, it was related to the installation being done from MSDN where the IIS setup was not completed. This has been resolved with the VFP 7 CD. So, I had to manually go in IIS and adjust some parameters.

Here is some information which has been transmitted to me by MS:

Configuring ISAPI Listener

When the ISAPI is installed, it registers itself to handle WSDL files. SoapToolkit 2.0 installation does this by creating an App Mapping to associate the .WSDL extension with soapisap.dll at the machine (server) level. If the App Mappings have changed at a lower node than the machine level (such as at the Web Site or Virtual Directory level) prior to Soap Toolkit 2.0 installation, then the newly added .WSDL mapping will not be inherited from the machine level settings. In this case you can manually enter the App Mappings at the lower level node using the IIS MMC Admin tool.
For example, these are the steps to manually add the App Mappings for the Default Web Site on IIS 5.0 using the IIS MMC Admin tool:

1. Select the Home Directory tab under the properties for the Default Web Site.
2. On the Home Directory tab click the Configuration button and select the App Mappings tab.
3. If the .wsdl extension does not exist, then add a new extension entry for .wsdl by clicking the Add button.
4. Enter the path to soapisap.dll. Note that because of a bug in the UI of the IIS Admin tool a pathname with spaces cannot be added. To workaround this problem enter the short-file pathname to the soapisap.dll (for example, C:\PROGRA~\COMMON~1\MSSOAP\BINARIES\SOAPISAP.DLL). Enter .wsdl in the Extension text box. For Verbs select Limit to and add GET,POST,HEAD. Finally, Script Engine should be checked and Check that files exist should be unchecked. Click OK to enter the new entry.