Like Windows DM, iODBC maps ANSI API calls to Unicode function calls. But unlike its Windows counterpart, it does not let driver know, that application is ANSI. That causes errors in charsets transcoding. We need to either figure out how to make it work, or simply split connector for iODBC into 2 - Unicode and Ansi drivers separately.