can't type in a shared database

[Kerry]

I have a database in a shared network drive. Specific people have access to
read/write and a few people have view only access.

The issue is that some users who should be able to read/write can't update
data, although our network people tell me they do have the correct access.
Also, they're not getting a message saying they have read only access as
other users do.

What could be causing these few users not to be able to update the database?

 

[Dale Fye]

In order for a user to be able to even open Access on a shared folder, he
must have read/write permissions to that folder (Access creates an ldb file
in the folder but cannot do this if the user does not have write permissions
in the folder where the application resides).

If you want to implement user level permissions (Read Only, Read/Write) you
have to have some code that either changes the AllowEdits property to
True/False for each user, or which locks/unlocks specified controls.

Dale

 

[Jerry Whittle]

1. All users of the database must have at least read, write, and modify
privileges to the folder holding the database file. Not just the database
..mdb file, but the entire folder. Again: ALL users.

2. Open the database and go to Tools, Options, and Advanced Tab. Set the
Default Open mode to Shared and the Default Record Locking to Edited Record.
(While you are in the Options area, go over to the General tab and turn off
Compact on Close and Name AutoCorrect. Trust me on this.)

 

[Kerry]

There are about 20 users with read/write access - only 2 have this issue.
There are also 5 users with read only permission - they aren't having any
issues. When the read only users open the database, they get a message
stating it's read only. When these 2 users open the database, they're not
getting the read only message, and they can view everything, but can't write.

Could this be a local issue on their PCs?

Months ago, when first implementing the database, I did try to put user
level security on the database, but it was only local. When opening the
database from any other PC, it signed in as admin and had full rights. I was
told this needs to be done on a network level, and except for these 2 users,
that seems to be working.