Re: Illegal access violation

Lists: pgsql-odbc
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
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: Bob Caryl <bob(at)fis-cal(dot)com>
To: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Illegal access violation
Date: 2005-07-26 14:52:44
Message-ID: 42E64E3C.2060401@fis-cal.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-odbc

Dave Page wrote:

>
>
>
>
>>-----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.
>
>
>
Hey Dave,

This was, apparently my problem. I was not using the correct version of
the obdc driver for WinXP. As to the updateable cursors issue: The
only operation I am doing here is adding records to a table back on my
linux routine. Upon opening my CRecordset object I do not even retrieve
any records, simply supplying the table name where one would normally
insert a query to retrieve rows. Hence, I am hoping that I don't run
afoul of any of the problem areas for updateable cursors. Assuming I'm
naive about this, I would love a URL to which I can point my browser for
more information on this subject.

Thanks!

Bob Caryl