Hi,

>>
Haven't received another message from you today, have you sent some code for me to try?
>>

Message seems to have disappeared. Essentially I suggested going back to basics and attempting this from the command line (don't use the _ws3client.vcx for the time being). Also don't worry about 'registering' the web service - that's just lets VFP generate sample code and make intellisense available. Just try:

oWs = CreateObject("MSSOAP.SoapClient30")
oWs.ConnectorProperty("Timeout") = 30000  && Give it plenty of time...
oWs.SetUpClient(.....)

and check the oWs properties to make sure you have no errors at this point. (I think from your last post that we're already happy that this is the case? )

>>Have you seen Geraint's reply on how the parameters should be specified?

Yes. I just looked at the VB sample code which is using a enum for SaleType (but to me that doesn't seem to gel with the wsdl). Anyway, on that basis, the VFP equivalent to .CreateSale(SaleType.PayMonthly) would be .CreateSale("0") (or you could try .CreateSale(0)). (SaleType.ThreePay) would be ("1"))

I wouldn't worry about VFP7 problems for now. If this is doable in VFP8 then there's no reason why it cannot be made to work in VFP7.

My other suggestions were to:
(a) hook in the MS Soap Trace utility (MSSOAPT.EXE) which will give you an exact look at what's actually being transmitted/received.
(b) if possible get someone to look at the server logs to determine if your request is actually hitting the server, etc..


HTH,
Viv