I'll try the odbc group. The combo boxes are populated from functions that
perform a standard query and don't take any parameters, so the calling code
is a very simple "Select * from queryfunc()" that returns an id column and a
The odbc group could probably advise if I should change something with
respect to the connection parameters if that is the issue.
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "George Weaver" <gweaver(at)shaw(dot)ca>
Sent: Monday, December 20, 2004 12:10 PM
Subject: Re: [NOVICE] Connection problem with 8 Beta 5
> George Weaver <gweaver(at)shaw(dot)ca> writes:
>> Faulting application test.exe, version 1.0.1813.27448, faulting module
>> psqlodbc.dll, version 18.104.22.168, fault address 0x0002001f.
> Certainly psqlodbc should be the first target of suspicion --- although
> it's possible this is caused by your code passing bad parameters to
> psqlodbc. In any case the ODBC guys can help you out better than anyone
>> Would this be an issue arising within my application? Is it a psqlodbc =
>> bug and should it be directed to the pgsqlodbc project as a bug? The =
>> Microsoft event log seems to point at psqlodbc but the database log =
>> seems to point at the application.
> The database server can't tell the difference between psqlodbc and your
> application code --- it's all "that stuff at the other end of the TCP
> connection" to the server.
> regards, tom lane
In response to
pgsql-novice by date
|Next:||From: Keith Worthington||Date: 2004-12-20 21:58:42|
|Subject: CAST and timestamp|
|Previous:||From: Kretschmer Andreas||Date: 2004-12-20 18:27:29|
|Subject: Re: Postgres version change - pg_dump|