Re: problem with CVS version

> -----Original Message-----
> From: Antonio Pennino [mailto:a.pennino@nocerainformatica.net]
> Sent: 27 July 2004 16:17
> To: Dave Page
> Subject: RE: [ODBC] problem with CVS version
>
>
> > Yes, because the older driver did not support unicode.
>
> my application is NOT unicode (never i have used unicode) and
> the table on the server not contain unicode fields but only
> "character varying(xx)".

Character varying(xx) may well be unicode depending on how your database
was created. With regard to your application, the ODBC Driver *Manager*
(ie. not the driver) will map function calls to the unicode version of
the functions (such as SQLDescribeColW) if it detects that your
application is unicode aware. Could it be the case that the MFC classes
you are using are unicode aware and the DM is detecting this?

Whatever the case though, the log file you supplied showed that you are
using the unicode functions (intentionally or not), therefore you should
expect to get unicode data types from the driver where appropriate.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/ht
m/odbcunicode_applications.asp

> Is possible to force the driver for
> not use unicode?

I assume you can just call SQLDescribeColA (or the A version of other
functions). This whole unicode/odbc thing is new to me anyway - I'm only
really trying to help out with ODBC bugs in the absence of anyone else
who *really* knows ODBC inside out, and I don't really have any personal
interest in ODBC these days anyway.

Regards, Dave.