Problem with multiple database users

[lelisec]

Hi All,
I have a database that is stored on a network drive. Usually more
than 1 person can be in the database at a time, but they may get an
error message about not being able to update something because another
user also in the database. However, there are a few people who are
never able to get into the database when another user is logged in.
Any idea what is going on?

Thanks in advance.

 

[Arvin Meyer [MVP]]

Make sure that the database is split and each user has a copy of the
front-end on their own workstation linked to the data on the server
(back-end). Also make sure that all settings are set to Shared in Tools >>>
Options

 

[Jerry Whittle]

In addition to Arvin's great suggestions, make sure that every user of the
database has Read, Write, Create, and Delete priviliges to both the database
file(s) and the entire folder holding those files on the network.

Also make sure that the .ldb file with the same name as the .mdb file goes
away when everyone is out of the database. If not, double check that EVERYONE
is out of the database then delete the .ldb file(s).

 

[David W. Fenton]

=?Utf-8?B?SmVycnkgV2hpdHRsZQ==?=

In addition to Arvin's great suggestions, make sure that every
user of the database has Read, Write, Create, and Delete
priviliges to both the database file(s) and the entire folder
holding those files on the network.

Strictly speaking, DELETE permission is not required. Before Access
95, Access never deleted the LDB file upon exit, and removing DELETE
permission simply leaves the LDB file doesn't get deleted by the
last user.

I always give administrative users DELETE permission so that they
can do compacts that would discard a bad LDB file, should it get
corrupted. But normal users don't need DELETE permission.

Why remove it?

So that a user can't delete the back-end data file.

 

[Guest]

who are you guise and what's this stupid database
thingy????????????????????????????