Could not update; currently locked (updated post)

  • Thread starter Thread starter slickdock
  • Start date Start date
S

slickdock

I am reposting, as I haven't been able to resolve this on previous posts. I
will combine all facts as I see them:

Using Access XP runtime application in a split database (front end and back
end): Users INTERMITTENTLY getting this error: "could not update, currently
locked"

This is coming from a continuous form, upon clicking on the last blank
record in the form, before typing text, the error message appears: "could not
update, currently locked."

The form's source table has a default field value on the [DateCreated]
field of Date(), and a default field value on the [TimeCreated] field of
Now(). Also, there is a default value on a combo box in the FORM's
[cboUserID] field, which is [Forms]![AA]![UserID]. And last, there is a
default value in the form's header on the hidden [MatID] field which is
[Forms]![Matters]![MatID]

When the user clicks on the last record's [txtComment] field in the
continuous form to start a new record, they immediately get the locked error.

Under tools, options, advanced, open databases using record level locking is
checked.


Please help if you can. THank you.
 
I'm concerned that I can't get a response on this. What is keeping people
away? Am I not being clear enough? I really need help. I have 60 users
getting this error at least once a day.
 
Using Access XP runtime application in a split database (front end and back
end): Users INTERMITTENTLY getting this error: "could not update, currently
locked"

This is coming from a continuous form, upon clicking on the last blank
record in the form, before typing text, the error message appears: "could not
update, currently locked."

Check to make sure you have Tools... Options... Advanced... Open Databases
using Record Locking checked. It may be locking a whole 4K byte block of
records, so that one user editing a new record (or the last record stored)
will block another user.
 
Thank you John, yes, it was already checked on the front end and on the back
end. What else should I do to resolve this?
 
Thank you John, yes, it was already checked on the front end and on the back
end. What else should I do to resolve this?

About all I can think of is:

1. You might have a Form and a Query, or two forms, attempting to edit the
same record at the same time.
2. You might have two users doing the same.
 
But this is when starting to type into a NEW record, not when editing a
previous record.
 
Any further ideas

Any further ideas on this problem? I am having the exact same thing as described above - with one additional caveat.

The form for each user is filtered to only see their records. I have the user's name in a field on the main form that is used as the default for the user field in the record.

When users go to create a NEW record, they get the "Could not update; currently locked" message.

It appears to affect some users/PCs more than others, but this may be coincidence.

My rollout is currently at a standstill as a result of this issue - any assistance would be much appreciated.
 
Back
Top