The effect of Network rights on Access Apps

  • Thread starter Thread starter Lance McGonigal
  • Start date Start date
L

Lance McGonigal

Thanks in advance for your help.

I have an app that is split (Front/Back End). Some of the users have full
rights (network based) and some have read only to the folder. If a
read-only person gets in first then everyone is read only. If a full-access
person gets in first then the read-only folks get errors saying the table is
in use. I thought the rights would be respective to the user. Can anyone
give me a work around for this that doesn't use access security?

Thanks again.
 
Lance McGonigal said:
Thanks in advance for your help.

I have an app that is split (Front/Back End). Some of the users have
full rights (network based) and some have read only to the folder.
If a read-only person gets in first then everyone is read only. If a
full-access person gets in first then the read-only folks get errors
saying the table is in use. I thought the rights would be respective
to the user. Can anyone give me a work around for this that doesn't
use access security?

Thanks again.

For a shared database, all users must have full permissions on the
folder containing the database, so that the locking (.ldb) file can be
created, updated, and deleted. The locking file is necessary to
regulate shared access to the database; if it can't create it, then (I
believe) Access has no choice but to lock the entire .mdb file, so no
other user can be permitted to update the database, even if that user
has permissions on the folder.

I don't think there is any workaround that actually involves users
sharing the same back-end database file. You must give all users of a
shared database read/write/create/delete permissions on the folder
containing the file. If you want some users to have only read-only
access to the database, you should control it by workgroup security.
You can implement your own privilege-management scheme by using code in
the Open event of forms to examine the user's Network logon (or use your
own logon form), and make forms read-only as you choose, but it won't be
nearly as solid or effective as workgroup security.
 
Back
Top