From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Mark Morgan Lloyd" <markMLl(dot)pgsql-odbc(at)telemetry(dot)co(dot)uk>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Latest ODBC driver? |
Date: | 2006-08-28 16:14:10 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C880@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Mark
> Morgan Lloyd
> Sent: 27 August 2006 22:49
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Latest ODBC driver?
>
> Does this correspond to the versions of e.g. odbc32.dll as
> shown in the control
> panel?
No - it's just the version of the spec that the driver supports.
> Noted comment about the BDE- I'm still using that but trying
> to work to a point
> where I can junk it: IMO it's the worst of all worlds. On the
> other hand once I
> get rid of BDE I'm not sure whether I'll continue using ODBC
> or go direct. Are
> there any specific issues I should be watching out for with
> BDE and the ANSI
> driver?
No - it's th eUnicode one that disagrees with BDE - specifically,
text/varchar columns will all be empty if requested as Unicode strings -
which is exactly what BDE does because the driver offers that as the
default.
> Courtesy of Google hence
> http://www.installshield.com/news/newsletter/0411-articles/msi
exec.asp, the
> format appears to be
>
> msiexec /x psqlodbc.msi
/x and /uninstall are equivalent in Installer 3.x. I guess not in 2.x
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2006-08-28 16:21:32 | Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32 ANSI: psqlodbca Unicode: |
Previous Message | Hiroshi Saito | 2006-08-28 07:06:28 | Re: [COMMITTERS] psqlodbc - psqlodbc: Fixed dllname of win32 |