Re: Illegal access violation
От | Joel Fradkin |
---|---|
Тема | Re: Illegal access violation |
Дата | |
Msg-id | 002201c591ec$3a0606b0$797ba8c0@jfradkin обсуждение исходный текст |
Ответ на | Illegal access violation (Bob Caryl <bob@fis-cal.com>) |
Список | 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@postgresql.org [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Bob Caryl Sent: Tuesday, July 26, 2005 9:56 AM To: pgsql-odbc@postgresql.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? Thanks, Bob Caryl ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
В списке pgsql-odbc по дате отправления: