Hi Mike,

It turns out the compatibility layer is putting binary fields through the UTF-8 <> OEM conversion as well. We'll fix that for the next Alpha.

Regards,