Re: Usind database with encoding UNICODE and vovel - Mailing list pgsql-odbc

From Dave Page
Subject Re: Usind database with encoding UNICODE and vovel
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9812@ratbert.vale-housing.co.uk
Whole thread Raw
In response to Usind database with encoding UNICODE and vovel  (Josef Springer <Josef.Springer@JOOPS.COM>)
List pgsql-odbc

> -----Original Message-----
> From: Alejandro D. Burne [mailto:alejandro.dburne@gmail.com]
> Sent: 04 August 2005 16:11
> To: Dave Page
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: Usind database with encoding UNICODE and vovel
>
> 2005/8/4, Dave Page <dpage@vale-housing.co.uk>:
>
> ...
> > >
> > > Dave, thanks 4 your time;
> > > * I've installed MDAC 2.8 with same results.
> > >
> > > * If I don't set locale on the client it doesn't work,
> pgadmin either
> > > (show wrong encoding data)
> > >
> > > After connect trough odbc:
> > > SHOW CLIENT_ENCODING;
> > > return -> UTF8
> >
> > So to make it work, you do " SET client_encoding TO 'LATIN10' " ?
>
> Yes, I choose LATIN10 after odbc connect and things go ok, I'm using
> visualfoxpro.

OK, great thanks. Seems the sensible thig to try when you think about it
:-)

Regards, Dave.

pgsql-odbc by date:

Previous
From: Lothar Behrens
Date:
Subject: Re: SQLColAttribute and SQL_DESC_BASE_TABLE_NAME
Next
From: "Dave Page"
Date:
Subject: Re: Use Declare/Fetch in new version