Consultor Eletrônico

Status: Unverified

FACT(s) (Environment):

Progress 9.1D
Progress 9.1E
OpenEdge 10.0x
Crystal Reports
Windows

SYMPTOM(s):

Polish characters are not displayed in Crystal Reports

ODBC connection has been established from Crystal Report to a Progress database

Database has code page 1250

Database has been started with the following startup parameters:

-cpinternal 1250
-cpstream 1250
-cpcoll polish

Setting SQL_CLIENT_CHARSET system environment variable to 1250 has no effect

Polish characters can be displayed correctly in 4GL

Polish characters are displayed correctly in Crystal Reports when connected via JDBC

English language version of Windows is installed

Default codepage of operating system is 1252

CAUSE:

The ODBC drivers supplied with OpenEdge 10.0B and below are not Unicode-compliant. Therefore not all characters are converted properly. The correct behaviour is highlighted by the Unicode-compliant JDBC driver.

FIX:

Option #1
Set the operating system to use the 1250 code page. Once set, the correct Polish characters will be displayed in Crystal Reports.

Windows 2000
Start > Settings > Control Panel > Regional Options
Select the Set default... button from the Language Settings for the System section
Select Polish from the drop-down list in the Set System Locale dialog
Click OK to exit
Reboot (required by Windows) and re-test

Windows XP/2003
Start > Settings > Control Panel > Regional and Language Options
Select the Advanced tab
Select Polish from the drop-down list in the Language for non-Unicode Programs section
Reboot (required by Windows) and re-test

Note: If ODBC error -219901 is encountered, please refer to solution 21702 for more information.

Option #2
Upgrade to 10.1A

OpenEdge 10.1A has a new Unicode-compliant version of the ODBC driver which displays the correct Polish characters without having to adjust the system code page.