G
Guest
Hi Folks,
I have a form (frmBaseUnit) that periodically does not save a change to the
underlying record without producing any kind of a warning or error message to
the user. This is frustrating, since it only happens 2% of the time, and
requires calling up every record to double check in order to be sure a change
in field data has been saved.
The only thing I can think of is that other users of the database may be
firing off update queries (by virtue of an afterupdate event on a field on
another form) that somehow affects the same table on which frmBaseUnit is
also based through a query. I can understand how this might happen if the
same record was being updated, but this is not the case. After testing, I am
sure that the issue is happening even when different records in the
underlying table are being accessed simultaneously - one or some by an update
query, and an other via a manual record edit in frmBaseUnit.
I've search this newsgroup for former messages on update query interference
but don't see symptoms that match mine. They all seem to refer to a record
locking conflict.
Is there an obvious problem here? Or is there an intelligent process that I
can follow in order to narrow down the root problem?
Any and all suggestions would be greatly appreciated since I am about to
reuse the framework of the database for other projects and don't want this
problem to spread!
Thanks,
Jody
I have a form (frmBaseUnit) that periodically does not save a change to the
underlying record without producing any kind of a warning or error message to
the user. This is frustrating, since it only happens 2% of the time, and
requires calling up every record to double check in order to be sure a change
in field data has been saved.
The only thing I can think of is that other users of the database may be
firing off update queries (by virtue of an afterupdate event on a field on
another form) that somehow affects the same table on which frmBaseUnit is
also based through a query. I can understand how this might happen if the
same record was being updated, but this is not the case. After testing, I am
sure that the issue is happening even when different records in the
underlying table are being accessed simultaneously - one or some by an update
query, and an other via a manual record edit in frmBaseUnit.
I've search this newsgroup for former messages on update query interference
but don't see symptoms that match mine. They all seem to refer to a record
locking conflict.
Is there an obvious problem here? Or is there an intelligent process that I
can follow in order to narrow down the root problem?
Any and all suggestions would be greatly appreciated since I am about to
reuse the framework of the database for other projects and don't want this
problem to spread!
Thanks,
Jody