Consultor Eletrônico

Status: Unverified

SYMPTOM(s):

Data entered with Character client does not display extended characters on GUI client correctly.

Data entered with Character client does not display correctly on GUI client.

Extended characters do not display on GUI client.

CHANGE:

Upgraded application from version 8 to OpenEdge 10.

CHANGE:

Created new database in OpenEdge 10.

CAUSE:

The data entered by the character client is not using the correct code page. So the -cpinternal and -cpstream settings are set incorrectly when entering the data.

In this example the database is using the correct 1254 (Turkish) Windows code page, but the Character client is also using this code page for -cpinternal and -cpstream. Subsequently when characters are entered from the Character Client, because the -cpinternal setting of the client and the database are using the same code page there isn't any conversion performed when writing to the database.

This would be fine for a Windows GUI client, as this uses the Turkish Windows 1254 code page internally. The problem is that the Character Client session does not use this code page internally. It uses DOS based code pages, and in this case specifically the Turkish code page ibm857.

The result is that although the database is labelled as a Windows 1254 database, it actually contains ibm857 data.

FIX:

Start the Windows GUI client using the Windows code pages and start the Character client using the DOS code pages.

In this case start the Turkish Windows GUI client with:

-cpinternal 1254 -cpstream 1254 -cpcoll Turkish

and start the Turkish Character Client with:

-cpinternal ibm857 -cpstream ibm857 -cpcoll Turkish

The data entered with the old Character client settings should be deleted and re-added with the new Character Client settings.