database Exclusively (2000)

Topic

New Reply

Problem currently on one of the database running here,

firstly the db is set up with user level security so you are aware,

but heres the problem, too frequent the db is coming up with database locked exclusively by XXXXX .

my question is not so much how you sort this out, but more prevention.

There are two things which i know are causing this,

1. Users idea of logging out of night is to hit the powerbutton on the machine. These users are currently being re-educated in the form of being beaten by a yard stick every time they do this.

2. screensaver, darn screensavers come on after 5 minutes in this place (this is unchangeable )

any one got any tips for prevention measures i can take within the database, i have put in a time out function and that seems to have calmed it down a bit.

Reply | Quote

Replies

Make sure that all users have full permissions to the folder containing the database. If they don’t, they may not be able to create/delete the .ldb file that Access needs to keep track of who is using a database.

Make sure that standard users cannot modify/save the design of forms etc. Since you already use user-level security, that shouldn’t be too hard.

Reply | Quote

Make sure that all users have full permissions to the folder containing the database. If they don’t, they may not be able to create/delete the .ldb file that Access needs to keep track of who is using a database.

Make sure that standard users cannot modify/save the design of forms etc. Since you already use user-level security, that shouldn’t be too hard.

Reply | Quote

Sorry, but I don’t understand what the screensaver has to do with an exclusive lock on the database, even if the screensaver is password protected.

Is the message appearing when someone else tries to open the database, or what? There are several things that can cause this, but we need more information about the specific circumstances to determine which ones might apply. Is the database being opened through a shortcut, by double clicking in the explorer window, from a running instance of Access, or how? What kinds of permissions do your users have on the *folder* where the database resides? They need at least create, modify and delete permissions. Is this a split front end/back end application or a single app file in a shared location?

Reply | Quote

Trying to find where i read it now but apparently a frequently set screensaver can cause problems,

in answer to your questions,
The database is being opened by a shortcut on the user’s desktop
All users have modify permissions on the folder
Single database in a shared location (soon to be split)

The error is coming up about two or three times a day when users are loggin in. There are about 12 user’s using the database.

Reply | Quote

Modify permissions aren’t enough. They also need permissions to create and delete the ldb file. Without those permissions, you will encounter those exclusive lock errors.

Reply | Quote

Modify is read/write/delete

Reply | Quote

Thanks for the clarification, since the meaning varies between network and workstation operating systems.

Reply | Quote

Modify is read/write/delete

Reply | Quote

Modify permissions aren’t enough. They also need permissions to create and delete the ldb file. Without those permissions, you will encounter those exclusive lock errors.

Reply | Quote

You definitely want to split the database ASAP. One potential problem is that Access may think a user is trying to make a design change (i.e. apply a filter on a form or some other such action) and exclusively lock the database until that change is either saved or cancelled. For that reason it also highly desirable to deploy the Front-End to the user workstation, so that each user has their own copy of the database. There are some challenges in deploying changes in that situation, but it solves numerous other problems. As to the backup issue, there are backup programs that will backup a database even if it is open, and there are also commercial tools as well as some shareware that will let you boot out users that have been inactive for an extended period of time. Post back if you would like more info.

Reply | Quote

Hi wendell,

good advice, main reason i have been putting off the splitting of the database is due to their roll out policies at the place i work (who makes up these things ?) but hoping to do that soon.

I’ve been keeping a log of whoes logged in and when the system has been locking, have noticed a definate pattern there so going round to them today to give them a clip round the ear ole.

Reply | Quote

Hi wendell,

good advice, main reason i have been putting off the splitting of the database is due to their roll out policies at the place i work (who makes up these things ?) but hoping to do that soon.

I’ve been keeping a log of whoes logged in and when the system has been locking, have noticed a definate pattern there so going round to them today to give them a clip round the ear ole.

Reply | Quote

You definitely want to split the database ASAP. One potential problem is that Access may think a user is trying to make a design change (i.e. apply a filter on a form or some other such action) and exclusively lock the database until that change is either saved or cancelled. For that reason it also highly desirable to deploy the Front-End to the user workstation, so that each user has their own copy of the database. There are some challenges in deploying changes in that situation, but it solves numerous other problems. As to the backup issue, there are backup programs that will backup a database even if it is open, and there are also commercial tools as well as some shareware that will let you boot out users that have been inactive for an extended period of time. Post back if you would like more info.

Reply | Quote

Trying to find where i read it now but apparently a frequently set screensaver can cause problems,

in answer to your questions,
The database is being opened by a shortcut on the user’s desktop
All users have modify permissions on the folder
Single database in a shared location (soon to be split)

The error is coming up about two or three times a day when users are loggin in. There are about 12 user’s using the database.

Reply | Quote

Sorry, but I don’t understand what the screensaver has to do with an exclusive lock on the database, even if the screensaver is password protected.

Is the message appearing when someone else tries to open the database, or what? There are several things that can cause this, but we need more information about the specific circumstances to determine which ones might apply. Is the database being opened through a shortcut, by double clicking in the explorer window, from a running instance of Access, or how? What kinds of permissions do your users have on the *folder* where the database resides? They need at least create, modify and delete permissions. Is this a split front end/back end application or a single app file in a shared location?

Reply | Quote