Access 2016 locking on Sdrive

Question

Since a few days I want to start developing a new Access 2016 database.

But.. after leaving the .accdb file and return to it to continue, it locks the entire Database.

Saying another user has exclusive opened it.

Is this solvable? The Sdrive is the first suspect, because I have no problems working with it on C:

Which settings could be the cause? Never seen this before.

Answer 1

Is this a network installation (S drive?) where other users have access to the file? Typically if another user opens the database for exclusive access you will need to identify that person and have them close it so other users can access the database, or have a network administrator disconnect them.

---

Paul ~~~~ Microsoft MVP (Visual Basic)

Answer 2

Locks can be made through automation and other processes. This type of thing does happen, even to me, when in development when I get errors and I don't close connections properly ... This is part of development and tracking down issues and resolving them. That said, it should not happen in production. There things should be stable!

You have to see if the issue is reproducible, and if so, find the cause and address it.  Does this happen with a specific form, command, ... and go from there.

 

If you are new to Access database development, you may enjoy reviewing:

• http://www.devhut.net/2017/04/09/setting-up-an-ms-access-database/
• http://www.devhut.net/2017/04/20/access-best-practices-and-troubleshooting-steps/
• http://www.utteraccess.com/forum/Newcomer-s-Reading-List-t1998783.html

---

Daniel Pineault, 2010-2016 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 3

Sure, first thx for the reply. At the moment I've investigated that the software of the Seagate NAS is the problem; Seagate Access. After a cleanboot all worked fine here, but after running that service again 'old problems' return. Also is the explorer not working anymore.

(You have to refresh manually, no confirmation before deleting a file...)

So... I'm focusing on that matter first, and better use the external disk without his software.

The database wasn't in production yet :) after closing I did lock myself, and even worse, the database became corrupted at the NAS.

Again, thx for looking in it :)

Answer 4

Also thx to you Daniel,

As you can see, I made a reply to Paul, giving some more info.

Ofcourse I did exactly what you described and located the source of the problem.

Never seen this behaviour before (programming since 1978 :) )

Answer 5

I've had very mixed experiences with NAS drives and Access.  Your best bet is to place the BE on a share of of a PC or server.

---

Daniel Pineault, 2010-2016 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 6

I would tend to agree with Daniel. Access databases are sensitive to locking and corruption when running from network shares as it is, so adding NAS software to the mix is definitely not a good thing.

I'm not familiar with Seagate Access, but I would look for options to see if you can exclude the database from any monitoring or access.

---

Paul ~~~~ Microsoft MVP (Visual Basic)