RE: PostgreSQL, ODBC, Access - Mailing list pgsql-general

From Dave Burbidge
Subject RE: PostgreSQL, ODBC, Access
Date
Msg-id 01BFF61A.351F75A0.dburbidge@greyhoundswa.com.au
Whole thread Raw
In response to PostgreSQL, ODBC, Access  ("Jeffrey A. Rhines" <jrhines@email.com>)
List pgsql-general
Greetings!

I have seen similar (too often for my liking) while trying to update data
directly in a linked table/datasheet via MSAccess ... I've tried to work
out why, and it just isn't logical (while changing a set of contiguous,
related records, some will come up with this error, some won't) ...
However, if I use an (Access) update query, or do it in VisualBasic, it
works fine.

Note that this problem occours with other SQL Servers (including MS SQL),
so it's not the fault of the server.

Basically, don't use datasheets - MSAccess / ODBC does something odd with
the locking.

Dave Burbidge
Network Administrator

> -----Original Message-----
> From: Jeffrey A. Rhines <jrhines@email.com>
> To: pgsql-general@postgresql.org <pgsql-general@postgresql.org>
> Date: Monday, July 24, 2000 11:21 AM
> Subject: [GENERAL] PostgreSQL, ODBC, Access
>
> Hello All,
>
> Here's a bothersome issue:  I've got the most recent versions of
> Postgres, ODBC client for Win32, and Access 97.  My client can enter new
> records fine via a linked table.  However, when she goes back to add
> data to a column, she gets the following error:
>
> message box title: "Write Conflict"
> description: "This record has been changed by another user since you
> started editing it.  If you save the record, you will overwrite the
> changes the other user made."
> buttons: "Copy to Clipboard" and "Drop Changes".
>
> She is the only person using the database at the time.  The column type
> doesn't matter, either.  Does anyone know what causes this?
>
> Best Regards,
> Jeff Rhines



pgsql-general by date:

Previous
From: Chris Bitmead
Date:
Subject: Re: 4 billion record limit?
Next
From: "Timothy H. Keitt"
Date:
Subject: Re: Statistical Analysis