From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Bob Caryl" <bob(at)fis-cal(dot)com>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Illegal access violation |
Date: | 2005-07-26 14:02:15 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9544@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 Bob Caryl
> Sent: 26 July 2005 14:56
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: [ODBC] Illegal access violation
>
> Hello all:
>
> I am using the latest version of postgresql (version 8.03) on a linux
> machine as my server. I also using the latest version of the
> postgresql
> odbc driver (08_00_0101) on my WinXP platform. I have updateable
> cursors enabled on the odbc driver. I am trying to simply
> add a new row
> to my table on the linux machine, and when I call the
> CRecordset::Update
> method my application crashes with a memory access violation every
> time. Using the debugger and stepping through the code, the crash
> apparently happens in the .dll code. According to logs client and
> server side, this crash occurs before any attempt is made to
> do anything
> server-side.
>
> Has anyone else seen this, and if so what might I be doing wrong here?
The updateable cursor option is known to be a little unstable (which is
why it's marked experimental). Can you please try the latest libpq based
driver from http://www.postgresql.org/ftp/odbc/versions/snapshots/ and
see how it performs please?
Regards, dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Fradkin | 2005-07-26 14:13:41 | Re: Illegal access violation |
Previous Message | Bob Caryl | 2005-07-26 13:56:15 | Illegal access violation |