Problem:

User tries to save changed data and gets the following error, even though
there is no other user in the record:

"Could not update; currently locked."



Application structure:

An mdb file containing all of the tables & and mde file containing all of
the queries, forms, and modules, and uses table links. Users enter the
application via a shortcut to the mde file. (The record level locking
parameter is turned on.)



Problem scenario:

The form that usually encounters the problem is a filtered form with sub
forms. The user clicks a button on the form to add new records, which runs
VB code inserting records in several tables. Then the form is refreshed and
repositioned to the new data. They change some data then encounter the
error when saving it. Usually occurs with many users (10) accessing it,
however they aren't usually in the same data record as the user encountering
the error. Most of the time the user can wait a while, or exit and go back
into the application, and then is able to save the data.



I can't replicate the condition with test files, because I can't emulate the
large usage.

The only thing I can do is trial and error changes to production during the
peak usage times, which is not ideal.



Any suggestions would be appreciated.



Access 2000 or 2002

David French wrote:
> Problem:
>
> User tries to save changed data and gets the following error, even
> though there is no other user in the record:
>
> "Could not update; currently locked."
>
>
>
> Application structure:
>
> An mdb file containing all of the tables & and mde file containing
> all of the queries, forms, and modules, and uses table links. Users
> enter the application via a shortcut to the mde file. (The record
> level locking parameter is turned on.)
>
>
>
> Problem scenario:
>
> The form that usually encounters the problem is a filtered form with
> sub forms. The user clicks a button on the form to add new records,
> which runs VB code inserting records in several tables. Then the
> form is refreshed and repositioned to the new data. They change some
> data then encounter the error when saving it. Usually occurs with
> many users (10) accessing it, however they aren't usually in the same
> data record as the user encountering the error. Most of the time the
> user can wait a while, or exit and go back into the application, and
> then is able to save the data.

As I recall Access does not lock "records" rather it locks "pages." A
page may be one record or many depending, I guess, on the size of the
records.

I suspect that is your problem. The few times I can into locking
problems I switched to batch processing so the data was actually added to
the front end temp table and then that data was used to update the back end
table at the end of the data entry operators session.

>
>
>
> I can't replicate the condition with test files, because I can't
> emulate the large usage.
>
> The only thing I can do is trial and error changes to production
> during the peak usage times, which is not ideal.
>
>
>
> Any suggestions would be appreciated.
>
>
>
> Access 2000 or 2002

--
Joseph Meehan

Dia duit