Hello ML wizards, I wonder how the conversion works between UCS2 and WINDOWS-932(MBCS, Multi Byte Character Set). I'm Japanese, and I usualy use WINDOWS-932 encoding on Windows. When I do ODBC calls to get Japanese data, conversion errors occur.
For example, using column names in Japanese with Unicode Instance, when I call the ODBC call to get the name (e.g. SQLGetData() with SQL_C_CHAR for TargetType), the error 07006(Restricted data type attribute violation) returns from ODBC. (MaxDB 7.6.00.16 on WindowsXP Professional) I took a look at the source, and figured out the conversion (UCS2 -> WINDOWS-932) is processed in sp81AnyUCS2toASCII(). But because the converting codepage is for SBCS(Single Byte Character Set), the conversion of Kanji characters(2 byte per character) to WINDOWS-932 fails. Does't MaxDB ODBC driver support MBCS? I guess the conversion between UCS2 and MBCS should be supported. Best regards, Yasuo Ohtomo from Japan PS. I've tried to modify the source for MBCS conversion, and have attached the diff file for what I have working for me.
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
