OK I will try pgadmin III beta I think it is stable enough for me.
Nevertheless if I execute
SET CLIENT_ENCODING = LATIN1;
in an SQL Window the character display is fine even in pgadmin II
since the translation is (I guess) done by the server process and
vb just diplays character it can display.
So I thought the ConnSetting does the same but it seems not
to be used.
Thank you,
Claus
----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
<snip>
The problem is not the DSNless connection, but rather the fact the VB
(in which pga2 is written) will not handle Unicode. Beleive me, if it
did, the connection string would be set as required :-)
<snip>