Hi Leroy,
With most web services, the devil is in the details, and not unlike any programming it's the stuff that's _not_ documented that really causes the problem. The fastest way to get going is to get a working client as an example. From this example, using Fiddler, you can inspect the packets being sent, and returned, and that'll make the job a LOT easier.
The next step is to take the NetTalk example SOAP client, with xFiles, and send a simple request to the server. And inspect the reply.
Now this may seem daunting, but actually it's remarkably easy. It's the "unknown" that is scary - but the process itself is really simple.
All you're really doing is
a) form an appropriate clarion structure (almost always a GROUP) which contains the fields for the request.
b) use xFiles to turn the structure into Xml. (The xFiles doc section on Saving,
http://www.capesoft.com/docs/xFiles/xfiles.htm#CreatingXML, is especially useful here.
And the instructions on setting properties is particularly important
http://www.capesoft.com/docs/xFiles/xfiles.htm#PropertiesInSave)
c) POST the xml to the remote service using the WebClient class.
d) then handle the reply.
Cheers
Bruce