Mark Morgan Lloyd wrote:
> After the flurry of activity a few weeks ago and the much-appreciated help I
> started investigating what versions of ODBC (etc.) DLLs would work with NT4, in
> the hope that I could standardise on a particular set of files on all NT4
> machines. I fairly rapidly found that this was a bit of a minefield and started
> missing the capability I have on Linux to roll back changes to a known point, so
> undertook a major digression setting up NT4 running in a guest Qemu session. To
> cut a long story short, the PostgreSQL ODBC drivers didn't work in that
> environment, so I set up another clean copy of NT on a sacrificial machine...
> and found things still didn't work :-(
>
> Unless otherwise stated I'm running NT4W SP6a, IE 4.01 SP1 and NT hotfixes as
> per Q299444. As a further prerequisite I've installed the PostgreSQL ODBC
> drivers 7.02.0001 then de-installed them, this leaves a copy of msiexec.exe on
> the system. I'm calling this the baseline; I have no reason to believe that this
> configuration is broken, but it does not have the same usage history as most
> live or development systems around here.
>
> Current PostgreSQL ODBC is assumed to be v8.02.0100 with update DLLs downloaded
> today (17th October) from
> http://www.geocities.jp/inocchichichi/psqlodbc/index.html.
>
> If I take the baseline system and install Postgres ODBC 8.02.0100 plus the
> update DLLs from mid September, I get a "General SQL Error" with a BDE error
> code of 13059 if I try to open a database using the BDE administrator. Updated
> to the latest DLLs I get "General SQL Error. Missing server name, port or
> database name in call to CC_connect" with "BDE Error
Could yo send me the mylog and commlog(qlog) for the case ?
regards,
Hiroshi Inoue
