Re: MS Access, Unicode, Conversions & Foreign languages characters - Mailing list pgsql-odbc

From Ropel
Subject Re: MS Access, Unicode, Conversions & Foreign languages characters
Date
Msg-id 008701c3b384$93ba7030$0100a8c0@ropelxp
Whole thread Raw
In response to Re: MS Access, Unicode, Conversions & Foreign languages characters  ("Philippe Lang" <philippe.lang@attiksystem.ch>)
List pgsql-odbc
About speed improvements: I've noticed more than once that exporting,
dropping, creating and restoring a database I obtain a consistent speed
improvement not reachable with just vacuum analyzing.
I'm just planning to see if index clustering o reindexing can give the same
effect without throwing away and recreating everything (this second
operation is obviously possible only putting the DB off-line and I refuse
doing such a thing just for speed improvements, what if I need to operate
with HUGE DB ??!!!)



----- Original Message -----
From: "Philippe Lang" <philippe.lang@attiksystem.ch>
To: "PostgreSQL ODBC" <pgsql-odbc@postgresql.org>
Sent: Tuesday, November 25, 2003 6:03 PM
Subject: Re: [ODBC] MS Access, Unicode, Conversions & Foreign languages
characters


Hi,

Just in case it could help anyone: when you create a database in PG, you can
specify an encoding. For french, I use LATIN1, and the result is perfect. I
can see the accents in Access, with the latest (non-unicode) ODBC driver.

But that's not all! I have noticed an huge speed improvement. The database
was quick before, now it is even better. A database that needed more than 20
seconds to be created now only needs 5 seconds. Can that be due to the new
encoding, or to the fact I have dropped and created the database again?



-----Message d'origine-----
De : Philippe Lang
Envoyé : dimanche, 16. novembre 2003 14:24
À : PostgreSQL ODBC
Objet : [ODBC] MS Access, Unicode, Conversions & Foreign languages
characters


Hello,

Did anyone find a solution to the problem of foreign languages character
encoding, when data is accessed through MS Access 2000? Characters with
accents appear correctly in PG Admin 3.0, but not when they go through ODBC.

I have read different things on the subject: The drivers supports Unicode
UTF-9, but Access requires Unicode UCS-2, for example.

Is there a workaround, for example by forcing a special encoding when doing
a "CREATE DATABASE", or by using a "CREATE CONVERSION"?

I'm using the latest driver.

Thanks

-------------------------
Philippe Lang
Attik System
http://www.attiksystem.ch

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend



pgsql-odbc by date:

Previous
From: "Philippe Lang"
Date:
Subject: Re: MS Access, Unicode, Conversions & Foreign languages characters
Next
From: "Patrick Hatcher"
Date:
Subject: strange behavior