Hi everyone,

We have a VFP table with a Memo Binary field that contains plain text. We are running into an issue where once in a while when we pull the data through ODBC it converts the text to what appears to be a double-byte character set / Kanji instead of normal text. When we change the field to a plain Memo it work fine. We need to use the field as Memo Binary because we are now compressing the data for this field but need to be backwards compatible.

Any ideas why a Memo Binary field would show double-byte chars for plain text for a scattered few records through ODBC? When we do the same SQL SELECT from a VFP command window it displays the text correctly. We looked closely at the contents of the field for those records and didn’t see any CHR(0) or other weird characters?

Thanks!