The € is saved as ¿.
The € is saved as ¿.
Hello,
I have Rad Studio 2007, dbexpoda40.dll (4.20.0. and Oracle 11g.
I upgrade the dbexpoda40.dll to the last version (4.90.0.25) but the sign "€" is always convert in "¿". The old version works fine.
The charset of the database is "FRENCH_SWITZERLAND.WE8ISO8859P1".
Is it possible to have the same behaviour with theses two versions?
I have Rad Studio 2007, dbexpoda40.dll (4.20.0. and Oracle 11g.
I upgrade the dbexpoda40.dll to the last version (4.90.0.25) but the sign "€" is always convert in "¿". The old version works fine.
The charset of the database is "FRENCH_SWITZERLAND.WE8ISO8859P1".
Is it possible to have the same behaviour with theses two versions?
Last edited by Vincent P on Wed 14 Sep 2011 15:59, edited 1 time in total.
Hello,
It's a problem of charset. We create a new database with UTF-8 charset. The symbol € is saved correctly. But we cannot changed the charset of all customer's DBs for a upgrade of the dbexpoda40.dll.
I will discuss with my database administrator to create the database script.
Best regards
EDIT: I send you delphi sample and the script to create the database.
It's a problem of charset. We create a new database with UTF-8 charset. The symbol € is saved correctly. But we cannot changed the charset of all customer's DBs for a upgrade of the dbexpoda40.dll.
I will discuss with my database administrator to create the database script.
Best regards
EDIT: I send you delphi sample and the script to create the database.
Hello,
The symbol of Euro (€) is supported in the following encodings:
AL24UTFFSS
AR8MSWIN1256
BLT8MSWIN1257
CL8MSWIN1251
D8EBCDIC1141
DK8EBCDIC1142
EE8MSWIN1250
EL8ISO8859P7
EL8MSWIN1253
F8EBCDIC1147
I8EBCDIC1144
IW8MSWIN1255
S8EBCDIC1143
TR8MSWIN1254
UTF8
WE8EBCDIC1140
WE8EBCDIC1145
WE8EBCDIC1146
WE8EBCDIC1148
WE8ISO8859P15
WE8MSWIN1252
WE8PC858
Your encoding (WE8ISO8859P1) does not support this symbol. You can get more information on Oracle Metalink at http://metalink.oracle.com/metalink/pls ... id=68790.1
P.S. Maybe you had a different database encoding before.
The symbol of Euro (€) is supported in the following encodings:
AL24UTFFSS
AR8MSWIN1256
BLT8MSWIN1257
CL8MSWIN1251
D8EBCDIC1141
DK8EBCDIC1142
EE8MSWIN1250
EL8ISO8859P7
EL8MSWIN1253
F8EBCDIC1147
I8EBCDIC1144
IW8MSWIN1255
S8EBCDIC1143
TR8MSWIN1254
UTF8
WE8EBCDIC1140
WE8EBCDIC1145
WE8EBCDIC1146
WE8EBCDIC1148
WE8ISO8859P15
WE8MSWIN1252
WE8PC858
Your encoding (WE8ISO8859P1) does not support this symbol. You can get more information on Oracle Metalink at http://metalink.oracle.com/metalink/pls ... id=68790.1
P.S. Maybe you had a different database encoding before.
We know this problem. We have chosen this charset a long time ago and now it's not easy to change it for old customers. For new customers we have the UTF8, and it's work good.
With the dbexpoda40 V4.20.0.8 the character isn't converted.
With the dbexpoda40 V4.90.0.25, the character is converted to ¿ by the dbexpoda40.dll. I supposed the dll reflects the charset of the database.
Is that possible to deactivate this automatic conversion???
With the dbexpoda40 V4.20.0.8 the character isn't converted.
With the dbexpoda40 V4.90.0.25, the character is converted to ¿ by the dbexpoda40.dll. I supposed the dll reflects the charset of the database.
Is that possible to deactivate this automatic conversion???
Hello,
We've reproduced the problem.
In the old driver versions the server charset page was taken, and that's why the Euro symbol could have been displayed correctly. But in practice such behavior turned to be wrong, and in the new versions of the driver we take the charset page from the regional settings of the current PC in the Direct mode, and from the client settings in the OCI mode.
To solve your problem, you should set the encoding explicitly in the Charset property:
SQLConnection1.Params.Values['Charset']:= 'WE8ISO8859P1';
We've reproduced the problem.
In the old driver versions the server charset page was taken, and that's why the Euro symbol could have been displayed correctly. But in practice such behavior turned to be wrong, and in the new versions of the driver we take the charset page from the regional settings of the current PC in the Direct mode, and from the client settings in the OCI mode.
To solve your problem, you should set the encoding explicitly in the Charset property:
SQLConnection1.Params.Values['Charset']:= 'WE8ISO8859P1';