Yes, that's what I'm doing. That part works fine. The error happens when I try to call a method on the service that returns data. It works fine on XP.

The error is:
OLE IDispatch exception code 0 from Connector: Connector:Connection time out. HRESULT=0x800A1527 - Client:An unanticipated error occurred during the processing of this request. HRESULT=0x800A1527 - Client:Sending the Soap message failed or no recognizable response was received HRESULT=0x800A1527 - Client:Unspecified client error. HRESULT=0x800A1527..

Here's the web.config:

<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
	<system.serviceModel>
		<services>
			<!-- Before deployment, you should remove the returnFaults behavior configuration to avoid disclosing information in exception messages -->
			<service name="WCFData.DataService" behaviorConfiguration="returnFaults">
				<endpoint contract="WCFData.IDataService" binding="basicHttpBinding"/>
				<endpoint contract="IMetadataExchange" binding="mexHttpBinding" address="mex" />
			</service>
		</services>
		<behaviors>
			<serviceBehaviors>
				<behavior name="returnFaults">
					<serviceDebug includeExceptionDetailInFaults="true"/>
					<serviceMetadata httpGetEnabled="true" />
				</behavior>
			</serviceBehaviors>
		</behaviors>
	</system.serviceModel>
	<system.web>
</configuration>

>I'm getting SOAP errors trying to connect to a WCF web service running on localhost. My first thought it that the SOAP Toolkit doesn't work properly on Vista. I can consume the WSDL and generate the Intellisense scripts and program stub. The error happens when I try to call the web service. Anyone know why I'm getting errors?
>
>Hi, Craig,
>
>I'm able to consume a WCF web service on Vista using VFP - here's the code that I have:
>
>

>loWSHander = NEWOBJECT("WSHandler",HOME()+"FFC\_ws3client.vcx")
>
>loBasicHttpBinding =
>    loWSHander.SetupClient("http://localhost/WCFDemo/Service.svc?wsdl",
>                                    "DemoService", "BasicHttpBinding_IMyService")
>
>

>
>Is that what you're doing? What kind of error are you getting, and what does your web.config file look like?
>
>kevin