The UnicharBind database parameter enables you to bind strings as Unicode.
ASE, SYC Sybase Adaptive Server Enterprise
UnicharBind=value
UnicharBind=1
This parameter is designed to prevent data loss when an application sends Unicode data to a non-Unicode database. If the database server supports the unichar data type, you can bind strings to Unicode by setting this parameter to 1. UnicharBind is set to 0, InfoMaker always sends Unicode strings as Unicode. If the receiving database does not support Unicode (for example, the string is stored as unichar or univarchar data, data can be lost.
When UnicharBind is set to 1, if the database server supports unichar, strings are bound as Unicode. client and database server character sets are different an, the database interface converts Transact-SQL, identifiers, parameters, and Char and VarChar data to and from the character set used on the server. Multiple languages are not supported with this setting.
The parameter can be set dynamically at runtime after connecting to a database.
To enable multilanguage support, you must set the UnicharBind database parameter to 1 and the database server must have the UnicharBind character set installed, or, for Adaptive Server, it must be configured to support Unicode conversions. To do so, the database administrator must run the following command on the server:
sp_configure "enable Unicode conversion", 2
This enables the server to perform the conversion to and from Unicode.
To specify that the database server you are accessing with InfoMaker uses UnicharBind as its default character set, select the UTF8 Character Set Installed or Unicode Conversion Enabled check box on the Regional Settings page in the Database Profile Setup dialog box.