Not Exclusive access

[plaguna]

Is there a way to make changes (updates) in an access file which doesn’t have exclusive access? This file is in a network shared folder, and when somebody opens the file first, he/she has Write + Read Attributes and, the rest of the users have Read Only. This doesn’t allow making important changes when we need. Not until everybody is off. It is becoming an issue because a lot of people need to open this file at any time and/or at the same time. Any suggestion to solve this problem will be greatly appreciated.
Thank you in advanced

Plaguna

[DonRayner]

Is there a way to make changes (updates) in an access file which doesn’t have exclusive access? This file is in a network shared folder, and when somebody opens the file first, he/she has Write + Read Attributes and, the rest of the users have Read Only. This doesn’t allow making important changes when we need. Not until everybody is off. It is becoming an issue because a lot of people need to open this file at any time and/or at the same time. Any suggestion to solve this problem will be greatly appreciated.
Thank you in advanced

Plaguna

Try Tools-Options-Advanced... Make sure that the "Open database with record level locking" checkbox is checked and then just above that set the default record locking to "edited record"

[plaguna]

I tried what you suggested and, for some reason It still doesn’t work.

[DonRayner]

I tried what you suggested and, for some reason It still doesn’t work.

You need to setup user level security on your database so that users will have to log in with a user id and password. If you are not using the security then the database will treat everyone who logs in as the same default user. Is your database one access mdb file that is shared out or do you have it split into a front end and back end?

[NeoPa]

Any time you try to make any design changes to objects in your database it will change the open mode of the database to exclusive.

It's not a good idea to make such changes to a live / production database. I suggest you keep a development / test copy where changes are made and release changes when the database is otherwise unused.