Its SQL_ASCII at both ends here too.
The characters in question are the literal representation of “ ”
... Yahoo! Mail may have translated those characters in my email to plain ol'
double-quotes, which are benign.
CG
--- Dave Page <dpage@vale-housing.co.uk> wrote:
>
>
> > -----Original Message-----
> > From: Chris Gamache [mailto:cgg007@yahoo.com]
> > Sent: 14 April 2004 16:06
> > To: Dave Page; pgsql-odbc@postgresql.org
> > Subject: Re: [ODBC] New driver snapshot - 07.03.0209
> >
> > I gave the 7.3.2.9 driver a whirl. The first thing that I
> > notice is that some characters aren't displayed as they used
> > to be... For instance "testing" yields
> >
> > ?esting? ... This is presumably due to the use of the unicode
> > driver as the new standard driver. That shouldn't be a
> > problem. There's probably a setting that I'm missing. I've
> > tried using the set client_ecnoding='SQL_ASCII' in the
> > connection string without any effect.
>
> What's the server encoding? I'm not seeing any problems here with
> SQL_ASCII at both ends....
>
> Regards Dave.
__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html
