Errors - programming versus hardware

[Sandy]

Often when we try to select an option from a drop down list of our Access
client records to add the data to another record, the system locks up and
gives us an error message such as "The Microsoft Jet database engine stopped
the process because you and another user are attempting to change the same
data at the same time" which is not true. If we exit, then reopen the
record, the correct data is in the field.

Our designer says this is a switch issue. Our IT says it is a code issue.
We, the users, are in the middle dealing with a frustrating problem. Any
help would be appreciated.
Sandy

 

[David W. Fenton]

Often when we try to select an option from a drop down list of our
Access client records to add the data to another record, the
system locks up and gives us an error message such as "The
Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same
time" which is not true. If we exit, then reopen the record, the
correct data is in the field.

Our designer says this is a switch issue. Our IT says it is a code
issue. We, the users, are in the middle dealing with a
frustrating problem. Any help would be appreciated.

It's a typical error that you would get if a programmer did this:

1. had controls bound to the form, and you've edited something
already, AND

2. the dropdown list has an AfterUpdate event that runs DAO code to
update the underlying data table via a SQL update.

Been there, done that.

In most cases, if you're working with a bound form, you shouldn't be
updating the tables used in it except via the controls on the form.
Mixing DAO updates with bound control updates is something that
simply isn't justifiable, except in the very rarest cases.

If you *must* do it, you have to make sure the form's edits are
saved *before* the code update runs. So, if your AfterUpdate of the
combo box is running code that updates the underlying table, put

Me.Dirty = False

before the update code is called. This will save the edits in the
form and eliminate the possibility of an edit conflict with the SQL
update.

Of course, this may not be the cause of your problem, but it's the
one I've seen most often as the cause of the error your report.

 

[Sandy]

Thank you very much. I think this will help.