We had this problem and tracked it down to the differences between Access's
and Posgres's handling of uninitialised booleans. The solution was to add
"set default false" on any booleans. Access does not set a default on
booleans in new rows it creates, but expects them to be not-null.
By the way, "write conflict" seems to be Access's message of last resort:
read it as meaning "something has gone wrong and I don't know what".
Peter Wilkinson
Innate Management Systems Ltd
-----Original Message-----
From: pgsql-odbc-owner@postgresql.org
[mailto:pgsql-odbc-owner@postgresql.org]On Behalf Of Hiroshi Inoue
Sent: 08 May 2001 01:19
To: Chris Gray
Cc: pgsql-odbc@postgresql.org
Subject: Re: [ODBC] ODBC and Access 2000
Chris Gray wrote:
>
> I'm running PostgreSQL on a Debian GNU/Linux box and have installed
> pgAdmin successfully on a Windows 98 machine. pgAdmin works fine for
> updating tables. I can use Access 2000 to insert a new row in a table.
> If I create an Access SQL query to update or delete a row, it works.
>
> If I try to delete or update a row using the data sheet view of a linked
> table I get a "write conflict" error or a message from the Jet db engine
> that another user is trying to modify the same data even though I'm the
> only one connected to the database.
>
> Any idea what's going on and how to stop it?
>
Which version of psqlodbc driver are you using ?
If it's older than 7.01.0003 please try the latest one.
regards,
Hiroshi Inoue
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
