>>>>>There appears to be a control character on the 13th line. Could that be it?
>>>>
>>>>I have converted that line to an empty string and it doesn't change anything. There is something else.
>>>
>>>Well, it turned out that it was indeed that line. The box character is creating the problem. I am looking for its equivalent to replace that. But, this brings an interesting question. What's the proper way of making sure no other characters like that create a problem in SOAP?
>>
>>What are you passing?
>>
>>If you have binary data (data that contains upper ASCII or CHR(0) for example) you need to pass your data as binary content, which is not trivial from VFP because we don't have native support for bytearrays. One way to do this is to encode the string into Base64 and use that string instead.
>
>It turned out that we had a character 1 as part of a message. I applied a verification for it.

We need another UT rule. No character 1's can be posted! <g>