Attached is a file with both mylogs enabled.Note: I have put the log through
a parser because the lines were only delimeted with a #10 instead of both
#10 and #13
Do I only need to replace the .dll files in order to upgrade the odbc
----- Original Message -----
From: "Ludek Finstrle" <luf(at)pzkagis(dot)cz>
To: "A.j. Langereis" <a(dot)j(dot)langereis(at)inter(dot)nl(dot)net>
Sent: Friday, December 23, 2005 1:12 PM
Subject: Re: [ODBC] Values in the select
> > And of mylog_2972.log
> Did you enable mylog output under both buttons (Global and DataSource)?
> It seems to me you don't or you didn't send me right mylog.
> This only connects and disconnects (like open DataSource options dialog).
> Please, enable mylog output in both dialogs (under Global and DataSource
> button). Delete all C:\mylog*.log after enabling mylog output.
> Than run you example app. There may appear mylog_XXXX.log in C:\
> There have to be SQLExecDirect or SQLExecute with your query in the
> mylog output. It's unuseable mylog in other cases.
> > Unfortunately I did not find version 08.01.0104 on the postgresql web
> > (http://www.postgresql.org/ftp/odbc/versions/msi/), where can I find it?
> It's not official release. It is development snapshot. Main psqlodbc
> site is hosted on pgfoundry.org (http://pgfoundry.org/projects/psqlodbc/).
> Development snapshot contains only psqlodbc[aw].dll. So you have to
> installed psqlodbc 8.01.0102 (latest official release) before.
> It could be enough to try psqlodbc 8.01.0102. And please send me mylog
> output from psqlodbc 8.01.0102 (not from 8.00.XXXX or even older).
> > I've tested it with the Unicode version and the same problem occours.
> Ok. It could speed up locating the problem.
Description: application/octet-stream (24.7 KB)
In response to
pgsql-odbc by date
|Next:||From: Campbell, Greg||Date: 2005-12-24 00:17:13|
|Subject: Re: ODBC connection string, MS Access|
|Previous:||From: Ludek Finstrle||Date: 2005-12-23 12:50:04|
|Subject: Re: Does postgresql-odbc work on 64-bit platforms?|