Are you using Row Versioning? This uses the xmin field so that it will be
necessary to relink the tables. MS Access can then use the primary key and
xmin to identify a row as exactly the same row it earlier retrieved. If you
don't do this access does uses all the fields (bar memo and BLOB's) in the
where condition of the update. This can lead to precision problems with
You will also need this in the back end to allow comparison of int4 to xid:
create function int4eq(xid,int4)
create operator = (
(Sorry if this is wrongly addressed as the mail digest sometimes contains
character sets my Outlook doesn't recognise and therefore just gives me one
big text file)
Error - Data changed by another user, Copy to Clipboard or Drop changes
I got the above error message various times and could not understand what
was causing it.
Finally we figured out that we had a numeric field with to many digits
beyond the decimal point and access was not able to handle it.
Instead of an inteligent error message though it claimed someone else had
changed the data.
The solution was to round the data down to something access could handle.
pgsql-odbc by date
|Next:||From: Maryann F Stopha||Date: 2001-07-18 18:44:28|
|Subject: Access 2000 and ODBC driver Data changed by another user, Copy toClipboard or Drop changes |
|Previous:||From: Henshall, Stuart - WCP||Date: 2001-07-18 08:09:32|
|Subject: FW: Data export using Microsoft Access|