- ODBC Driver does not convert multi-byte characters correctly if CharSet connection property is set to a multi-byte character set such as eucjis/sjis/utf8/big5.
- ASE's is using a single byte character set (such as cp850 or iso_1).
- You have inserted data including multi-byte characters such as sjis, eucjis, utf8, and big5 into tables on your ASE.
- You can display multibyte characters retrieved from the tables by using isql command with -Jcp850 or -Jiso_1 (i.e. server charset). However, the same multibyte characters are garbled when you retrieve them from the table by using ASE ODBC Driver
- SAP Sybase Software Developer Kit (SDK) 15.7
- SAP Adaptive Server Enterprise (ASE) Software Developer Kit (SDK) 16.0
- Adaptive Server Enterprise ODBC Driver by Sybase
Sybase SDK 15.7
ODBC, CharSet, CodePageType, ClientCharset, multibyte, multi-byte, Japanese, sjis, eucjis, utf8 , KBA , BC-SYB-SDK , SDK , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.