Took a look at that file, Wayne, and it looks just fine.

Did notice -- through the wonders of Google -- that a couple people seemed to suspect (unfortunately without a confirming certain resolution) SOAP version differences causing problems like this.

I remember having SOAP "issues" like this as well when fighting w/VFP auto WSDL generation. We ended up doing almost everything through SOAP 3.0 WSDL generator directly, thus avoiding the wall-banging headache with the VFP wizard. Then again, that was VFP 7 and SP1... so maybe things have gotten better?

Look on the bright side, tho'... .NET makes life so much simpler when creating and consuming XML web services!

---J

>I've recreated the xml file using the xmladapter, and massaged it every way I know how. The webservice is not mine... so I can't do anything to it - it was just recreated on another server, and still gives me the error.
>
>This was supposed to be easy - yeah right.
>
>If you don't mind, I sent you the xml file.
>
>TIA!
>