
November 16th, 2004, 07:08 AM
|
|
Registered User
|
|
Join Date: Nov 2004
Location: Stockholm, Sweden
Posts: 3
Time spent in forums: < 1 sec
Reputation Power: 0
|
|
|
Charset problems
Hi,
Working locally on Windows 2000 with Firebird 1.5.1 and Upscene dbExpress driver (InterXpress, trial). Also using IS_SQL and Marathon for admin purposes (trying them, among others).
Used Marathon to create a new database with charset WIN1252. Then connected to it using IB_SQL, specifying charset WIN1252. Works.
Then try to create a table "Företag" (note the national character "ö") using a SQL statement. Failed - can't transliterate. Why? I did specify the same charset WIN1252 everywhere.
Tried reconnecting with charset set to NONE. Then tried the create table again. Worked (as expected). I can see this table in IB_SQL if I connect with charset NONE, but not with charset WIN1252. With WIN1252 it throws transliteration errors at me (can connect, but error occurs when I try to open the DB browser in IB_SQL).
In Marathon I can see the table and work with it with charset WIN1252 specified. No problems at all there.
In my application with InterXpress, it seems to work like in IB_SQL - I can use the table with ServerCharSet NONE, but not with WIN1252.
Why does it work with Marathon and not with IB_SQL or InterXpress? How can I get it to work with InterXpress?
Thanks,
Kjell
|