Client applications typically disable character set conversion for one of the following reasons:
The client application needs to store and retrieve data in a character set that the server does not support.
The client application will itself perform any necessary character set conversion.
When character set conversion is disabled, Adaptive Server does not perform character set conversion on Transact-SQL statements, procedure, table, view and other names, or data. The server behaves as follows:
It assumes that Transact-SQL statements and names are in standard Transact-SQL.
It stores data values exactly as they are sent.
It generates messages in its default character set.
Client-Library applications can disable character set conversion for a connection by setting the CS_NOCHARSETCNV connection property to CS_TRUE before calling ct_connect to open the connection.
DB-Library applications can disable character set conversion for a connection by calling DBSETLCHARSET with char_set as NULL before calling dbopen to open the connection.
