Problems with multiple users Access 2003 running on Netware

[ChasGlasgow]

We have two groups of users, one who require to be able to update an access
database, the other who must not be able to do so. This was managed by file
rights on our Netware network and seemed to work ok. Something is now
causing this to fail. What happens now is that if any/all of the users with
write rights have opened the file, users with read-only rights get a 'could
not lock file' message. Also, if users with read-only rights manage to open
the file, then this forces it to open with read-only, for the users who have
write rights. Anyone who can offer any help will have my eternal gratitude.
Thanks in anticipation.

 

[Joshua A. Booker]

Chas,

I have no experience with netware, but this is the same for windows security
in my experience.

I don't think it's a good idea to open an Access db from a directory where
you only have read-only permissions. This has to do with the record locking
file that gets created when access opens (.ldb) Read-Only folks don't have
permission to create this file so if they open first, the db is read-only
for anyone. Also, I assume they can't write to the .ldb file so that's why
you get the 'could not lock'

It would be better to use Access security or use a different db for
read-only folks.

HTH,
Josh

HTH,
Josh

 

[Aaron G]

Chas,

It sounds like the folder properties where your db is located is set to not
give the "restricted users" read write permissions. When they try to access
the db, however, a new file (the lock file) need to be temporarily created.
They MUST have read write permissions.

I would have to test this, but it could be possible that the reason it's
been working so far is that an "admin user" accessed the file first and
thereby created the lock file. When the restricted user logged in next, the
lock file was in place and they weren't violating any rules.

The solution is to let Access handle the permissions. It's a small pain,
but will satisfy all your needs. You can actually get pretty granular with
permissions within your app once you set it up.

Go to Tools/Security... to start the process. It should be obvious, but
BACK UP your db before starting this process! You don't want to accidentally
lock everyone (including you) out for good!

HTH

Aaron G
Philadelphia, PA

 

[david epsom dot com dot au]

Start by removing the delete permission from the folder.

This will give you a persistent copy of the LDB file.

Then change the permissions on the LDB file to allow
everyone r/w/s/

Read users need to be able to write their computer name
to the LDB file, so that when there is a locking conflict,
Jet has a human-readable name to use in messages.

(david)