Thank you for your reply, Thomas, > did you try the Unicode ODBC-driver (sqlod32w.dll), which is usually > registered as "MaxDB (Unicode)" after installation? Then you could > receive the data as SQL_C_WCHAR and convert into codepages as you > wish.
Yes, it works fine to receive data as SQL_C_WCHAR, and the data is in UCS2. But, getting the data as SQL_C_CHAR with either Unicode ODBC-driver or Non-Unicode ODBC-driver from unicode instance, ODBC driver returns the error 07006. I wonder if I shouldn't get data as SQL_C_CHAR from unicode instance. I hope the ODBC driver returns the data in WINDOWS-932, when I call with SQL_C_CHAR. Best regards, Yasuo -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
