On 3 Jan 2011, at 8:12, Karen Springer wrote: > This particular record has consistently had a problem (though not always), > but users are unable to update other records as well. It doesn't occur with > all records though. Most of the time the updates work fine. I test > using a new Access DB that contains only a copy of this table and a form with > the BarCode and WorkOrder fields. There isn't any code behind the form.
Seeing that the access db is probably where both the data is altered and displayed at the same time, would it be possible that the problematic are in an open transaction somewhere? I'd imagine that in such cases access tries to perform an update, receives an error and changes the row contents back to what it was. You can look for open transactions and row locks in pg_stat_activity and pg_locks respectively. Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll see there is no forest. !DSPAM:737,4d2179a911543699029975! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
