Specifies whether string conversion between DataWindow Designer (Unicode) and the OCI client (multibyte) is based on the current OS code page or an Oracle character set.
O90 Oracle9i
O10 Oracle 10g
StrByCharset='value'
StrByCharset=0
The StrByCharset database parameter is ignored if NLS_Charset is set to Unicode because both DataWindow Designer and the OCI client use the UTF-16 format. When NLS_Charset is set to another value, you must set StrByCharset to 1 if the character set on the client is incompatible with the OS code page.
With these settings:
StrByCharset=0
Oracle Server NLS_CHARACTER='WE8ISO8859P1'
DataWindow Designer OCI client NLS_CHARSET='WE8ISO8859P1'
OS code page=1252
The Oracle client and server character sets match, so all string data from the client can be sent to the server and fetched back directly, even if some characters do not belong to the WE8ISO8859P1 character set but are within code page 1252, because no string conversion happens between the Oracle client and server. All string data can be displayed using the OS code page. If StrByCharset is set to 1, when string data is converted between the OCI client (ANSI) and DataWindow Designer (Unicode), characters that are not in the WE8ISO8859P1character set are not converted correctly.
With these settings:
StrByCharset=0
Oracle Server NLS_CHARACTER='US7ASCII'
DataWindow Designer OCI client NLS_CHARSET='US7ASCII'
OS code page=949 for Korean.
The client and server character sets match. All string data, including Korean characters, are sent or received one byte at a time so no data is lost. Using the Korean OS code page, all Korean string data can be converted from ANSI to Unicode safely with StrByCharset set to 0.
With these settings:
StrByCharset=1
Oracle Server NLS_CHARACTER='ZHT16BIG5'
DataWindow Designer OCI client NLS_CHARSET='ZHT16BIG5'
OS code page=1252
Because characters in the ZHT16BIG5 character set do not belong to code page 1252, string data conversion must be based on the ZHT16BIG5 character set.
To specify that the OCI client should use the current character set defined by the NLS_LANG parameter on the local computer to store string datatypes:
Database profile Select Local from the NLS Charset drop-down list and select the Use String Conversion Based on Oracle Character Set box on the Connection page in the Database Profile Setup dialog box.
Application Type the following in code:
SQLCA.DbParameter="NLS_Charset='Local',STRbyCharset=1"
