MS Access 2010 Database Engine Could Not Lock...

Hey friends,

My users are getting errors now with Access 2010 that they didn't get in previous versions.

There are times that I will be working on some queries in a separate .mdb file with links to the same BE that my users have and they will get an "Database Engine Could Not Lock... " error message. I'm not in the table design, just the query design.

Does any one know of a way that I can work in my copy of the .mdb and still let my users save data to those back end tables? This wasn't a problem in earlier versions.

Thanks for any help you can give me.

Eddie
LVL 5
eantarAsked:
Who is Participating?
 
eantarConnect With a Mentor Author Commented:
Hi all,

This error goes away when I take of the Lock Option in the OpenRecordset method of a DAO database in my vba code.

So I found the solution. But I'm willing to give points to anyone who can clearly explain this to me, or point me to an article I can read up on. All the best. E
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
If you're working with linked tables, then they shouldn't have any locks placed on them.

More likely is a permissions issue. All users must have at least Modify permissions on the folder hosting the database file. Even if you think you've checked the permissions - check them again, and then get someone else in the IT department to check them yet again.

Also be sure that a stray .ldb file is not floating around. Have everyone close out of the application and check the BE folder to see it a file with the .laccdb extension remains. If it does, delete it. If you can't delete it, then reboot the machine and see if it goes way.
0
 
eantarAuthor Commented:
Hey, thanks.

All the forms that they are using for data entry are set to Record Locks: No Locks. Is that what you mean?

Could you explain a little more about the permissions thing?

Remember that they have no problem till I have MY COPY (separate .mdb) open and I'm working in the Query Designer. That's when they get the "Could not lock" message.

E
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<My users are getting errors now with Access 2010 that they didn't get in previous versions.>>

  Depends on how far back were talking about.   Microsoft made a fundamental change in order to reduce corruption; you need exclusive Access to make design changes in a DB.

<<I'm not in the table design, just the query design.>>

 Note though that the table is still open even in query design.  I'm not sure why that should interfere with your users though, unless their trying to get exclusive use of a table.

 Follow what LSM suggested; check the basics first.

Jim.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
All the forms that they are using for data entry are set to Record Locks: No Locks. Is that what you mean?
No, I'm referring to Windows Permissions. If you are the one locking the database, then I'd start by reviewing the permissions of your user account for that network share.

It's also not uncommon for a corrupted user profile to cause issues like this. To test that, try logging in (on the same machine) as a different network user and see if you can perform the same tasks (you many have to temporarily create a new test profile on that machine, of course).
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<All the forms that they are using for data entry are set to Record Locks: No Locks. Is that what you mean?>>

 and FYI, "no locks" doesn't mean no locking at all.  It means no edit locks.    Locking is still occuring with records/pages with a form set that way.

Jim.
0
 
eantarAuthor Commented:
No one was really able to tell me why. So I'm closing the question.
0
All Courses

From novice to tech pro — start learning today.