The following bug has been logged online:

Bug reference: 1564
Logged by: Steinhaus, Harald
Email address: harald.steinhaus (AT) steinhaus (DOT) de
PostgreSQL version: 8.01
Operating system: Windows XP
Description: special Character OleDB
Details:

using charset SQL_ASCII German special characters are correctly shown in
pgAdminIII.
In a WindowsForms Application using PgOleDb-1.0.0.19 these characters are
shown as ? and removing the following character.

If required I can supply screenshots.

(Using other charactersets didn't allow use batchimport when the file
contains special characters

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

On Fri, Mar 25, 2005 at 10:43:08AM +0000, Steinhaus, Harald wrote:

If you are using SQL_ASCII, you should not insert non-7-bit-ascii data.
If you do, you are responsible for whatever may happen with character
conversion; which means, it will work on some cases, but will fail on a
lot of others.

You should really declare the correct character set at creation time
(which depends on the locale you choose), and issue the correct "SET
client_encoding" command at execution time.

Probably that's because you didn't define the correct client_encoding.
See the thread at

http://archives.postgresql.org/pgsql...3/msg00892.php

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Always assume the user will do much worse than the stupidest thing
you can imagine." (Julien PUYDT)

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