Hi,

I used:

Debian Sarge with PostgreSQL 7.4.7
My application on Win XP SP2
ODBC-driver: 08.01.1003

More or less the same problem with LATIN1 (server) and UNICODE (client)
but PgAdminIII doesn't show äöüß later.

Regards

Johann

Josef Springer schrieb:

Using no vovels (umlaut) work fine. But using a vovel, curious effect.
I have tried all server and client variations with sense with this result. All tests are done with a string column containing äöüß

Server database encoding
Client encoding
Result

LATIN
LATIN
Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0

LATIN
UNICODE Reading works bur witing gets an error 'Bad code xxx for UNICODE'

UNICODE
UNICODE
Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0

UNICODE
LATIN
Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0

UNICODE
WIN1250
Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0

SQL_ASCII
UNICODE
Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0

In PgAdminIII the column is displayed correct in all server database variations !

Server database encoding	Client encoding	Result
LATIN	LATIN	Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0
LATIN	UNICODE	Reading works bur witing gets an error 'Bad code xxx for UNICODE'
UNICODE	UNICODE	Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0
UNICODE	LATIN	Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0
UNICODE	WIN1250	Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0
SQL_ASCII	UNICODE	Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0