Skip site navigation (1) Skip section navigation (2)

Re: Illegal access violation

From: "Joel Fradkin" <jfradkin(at)wazagua(dot)com>
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:13:41
Message-ID: 002201c591ec$3a0606b0$797ba8c0@jfradkin (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
I am no expert, and am not sure what your app is, but you could try changing
your connection to allow logs (c:\mylog) , in this way you can see what is
happening and post it here for better analysis.
Debug=1 turns logs on in a dsn less connection.
For IIS you have to give permission for Iuser to write to the c drive.

Joel Fradkin


-----Original Message-----
From: pgsql-odbc-owner(at)postgresql(dot)org
[mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Bob Caryl
Sent: Tuesday, July 26, 2005 9:56 AM
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 

Has anyone else seen this, and if so what might I be doing wrong here?


Bob Caryl

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?


In response to

pgsql-odbc by date

Next:From: Bob CarylDate: 2005-07-26 14:52:44
Subject: Re: Illegal access violation
Previous:From: Dave PageDate: 2005-07-26 14:02:15
Subject: Re: Illegal access violation

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group