Hi Aaron,

>A method that I'm calling in a COM object is returning a delimited string that contains binary data. For some reason when the string is returned in VFP, all the characters between ASCII 128 and 159 have been changed to 63 (Question Mark).

The codes 128-159 only exist in the Windows codepages, but not in the commonly used "ISO 8859-1" encoding. It looks like there's some additional conversion going on aside from conversion from and to Unicode; or maybe some home-grown unicode conversion that strips of all character not starting with 0x00.

Maybe you can give a few more information, like in which language the COM object was written and what the interface definition for this method looks like. If this doesn't reveal a solution, you could write a VB wrapper that calls the COM object and have VFP call the VB object.

Christof