Hi,<br /><br /> I used:<br /><br /> Debian Sarge with PostgreSQL 7.4.7<br /> My application on Win XP SP2<br />
ODBC-driver:08.01.1003<br /><br /> More or less the same problem with LATIN1 (server) and UNICODE (client)<br /> but
PgAdminIIIdoesn't show <b>äöüß</b> later.<br /><span class="150583209-04082005"></span><br /> Regards<br /><br />
Johann<br/><br /> Josef Springer schrieb:<br /><br /><blockquote cite="mid42F1AFEC.1020906@joops.com" type="cite">
Usingno vovels (umlaut) work fine. But using a vovel, curious effect.<br /> I have tried all server and client
variationswith sense with this result. All tests are done with a string column containing <b>äöüß</b><br /><table
border="1"cellpadding="2" cellspacing="2" width="100%"><tbody><tr><td valign="top">Server database encoding<br
/></td><tdvalign="top">Client encoding<br /></td><td valign="top">Result<br /></td></tr><tr><td valign="top">LATIN<br
/></td><tdvalign="top">LATIN<br /></td><td valign="top">Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0<br
/></td></tr><tr><tdvalign="top">LATIN<br /></td><td valign="top">UNICODE</td><td valign="top">Reading works bur witing
getsan error 'Bad code xxx for UNICODE'<br /></td></tr><tr><td valign="top">UNICODE<br /></td><td
valign="top">UNICODE<br/></td><td valign="top">Writing works. Reading gets the bytearray 63.63,0,1,0,2,47,0<br
/></td></tr><tr><tdvalign="top">UNICODE<br /></td><td valign="top">LATIN<br /></td><td valign="top">Writing works.
Readinggets the bytearray 63.63,0,1,0,2,47,0<br /></td></tr><tr><td valign="top">UNICODE<br /></td><td
valign="top">WIN1250<br/></td><td valign="top">Writing works. Reading gets the bytearray
63.63,0,1,0,2,47,0</td></tr><tr><tdvalign="top">SQL_ASCII<br /></td><td valign="top">UNICODE<br /></td><td
valign="top">Writingworks. Reading gets the bytearray 63.63,0,1,0,2,47,0<br /></td></tr></tbody></table><br
/></blockquote><b>InPgAdminIII the column is displayed correct in all server database variations !</b><br /><br />
