Dave Page wrote:
> > 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.
OK, so if I read you correctly that's the version of the spec that the low-level
drivers tell the ODBC DLLs they're prepared to implement.
> > 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
OK, I think I've got an issue here relating to the BDE and the ANSI driver :-(
Running the failing program with the 8.01.0200 drivers and the 220.127.116.11 ODBC
DLLs memory usage explodes when it tries to execute the initial query, which is
basically there to establish communications with the tables. At present I think
that the problem is hidden somewhere inside the BDE but I'll see if I can
progress this further later.
Are there any connect settings that I need to know about that might be relevant,
or any other issues that anybody can recollect relating to the BDE?
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
In response to
pgsql-odbc by date
|Next:||From: Dave Page||Date: 2006-08-29 10:56:45|
|Subject: Re: Latest ODBC driver?|
|Previous:||From: anomatos||Date: 2006-08-29 08:45:02|
|Subject: Record locking issue using ODBC from .NET|