Multi-Users Causing Records to Lock - Help!

[franckh2]

Hi - I've got a database in Access 2007 that keeps track of client data for work. It's been working fine for about a month, and suddenly today other users can't change any information because the records are suddenly locked when accessed from their accounts.

I've already checked that they can't update forms, tables, nothing.

I've checked the database properties, it defaults to shared with no locks.

I've checked the properties of my forms - no locks.

I've double checked the permissions to the folder that the database is in - no restrictions.

The database is split.

I'm losing my mind! What is wrong here?!:banghead:

 

[David R]

Where is the frontend stored? Where is the backend stored? Only time I've ever hit this is a not-properly-split database.

Is there any funny 'Close' code on the database that would prevent it from giving up the lock?

 

[jdraw]

I agree with David, see
http://www.fmsinc.com/free/newtips/access/linkeddatabase.asp

 

[franckh2]

Thanks for the responses!

The front & back end are stored in the same folder under different subfolders.

I tried to run the code linked above but when my coworkers go to use the database it comes up that they don't have permission to access that database (i.e. the backend) or someone has it open & locked... which isn't the case as no one else is on it.

I double checked the backend... no locks, enabled.

Did I miss something?

 

[jdraw]

Are users sharing the FE? Each user should have his/her own copy of the FE on their PC.

 

[franckh2]

Yeah, they've been sharing the FE. We've got about 8 computers and they rotate. Everyone's gotta save it on every one, eh?

At any given point there's usually only 1 or 2 people on the database at once, and this problem is occuring with one person on.

 

[David R]

The front-end should be on their personal machine (unless you're running thin clients, obviously). This not only avoids the above problem, but speeds up loading times, as you're only transferring data across the network, not the FE itself.

If you find yourself having trouble keeping everyone's copy in everyone's profile on all eight machines (sounds like you have more than eight users?) up to date with changes to the FE, I recommend looking into bolarson's AutoUpdater. It will add a tiny bit of code that ... well, autoupdates the FE whenever they login next after changes have been made.