Access 2007: security on file-level does not work

[Guus]

Hello,
We have an Accessdatabase 'Lending.mdb' to loan books.
The database is placed on a networkdrive, called G:\General

All the users of our department are allowed to read/write files in the
folder "G:\General".

Now the database has been moved to folder G:\Automation.
In this folder all the users are just allowed to READ files.
Adminstrator has setup the rights for 'Lending.mdb' specific to read/write.

Although this rights, it is impossible to add/change records in the
Loan-database.
In Office/Access-2003 there was now problem to laon (so append/edit etc.).

Office-2007 seems to handle different with read/write rights.
What's usefull to change, so everyone using Office-2007 can still use
'Lending.mdb'?

Thank you in advance,
Guus

 

[Keith Wilby]

Hello,
We have an Accessdatabase 'Lending.mdb' to loan books.
The database is placed on a networkdrive, called G:\General

All the users of our department are allowed to read/write files in the
folder "G:\General".

Now the database has been moved to folder G:\Automation.
In this folder all the users are just allowed to READ files.
Adminstrator has setup the rights for 'Lending.mdb' specific to
read/write.

Although this rights, it is impossible to add/change records in the
Loan-database.
In Office/Access-2003 there was now problem to laon (so append/edit etc.).

Office-2007 seems to handle different with read/write rights.
What's usefull to change, so everyone using Office-2007 can still use
'Lending.mdb'?

Thank you in advance,
Guus

Users need write permissions to the host folder so that a record locking
file can be written to it. It sounds like your users are sharing an mdb
file. This is considered to be a bad thing. Multi-user apps should be
split, more info here:

http://www.granite.ab.ca/access/splitapp/index.htm

Keith.
www.keithwilby.co.uk

 

[Guus]

Excuse me Keith and other Office-expert,
I try to explain again my problem....

I have a lending database for the loan of books and software.
The database was originally created in Access version 2000.
The database works fine on a network for a group of employees.

All employees have read rights in the networkfolder "G:\Automation".

The database works perfect in Office 2003.
But now a number of colleagues already switched to Office 2007,
which is intended for all employees of the department.

The folder "G:\Automation" 's rights for all users is and will be "READ ONLY"
The database Loan.mdb in the folder has specific rights: "READ AND WRITE".

Despite these institutions, it seems impossible for the Office-2007
users to add records. In Office 2003 this was never a problem and
this problem is not there yet for Office 2003 users.

It seems that Office 2007 uses different rights.

REMEMBER: it is not an option for the administrator to place the database in
a
FOLDER with Read and write access. Sysadmin just want THIS
DATABASE read and write privileges.

I would like advice on how we can solve this problem.
Thanks,
Guus

 

[Keith Wilby]

The folder "G:\Automation" 's rights for all users is and will be "READ
ONLY"
The database Loan.mdb in the folder has specific rights: "READ AND WRITE".

I can only re-state that the host folder "G:\Automation" needs "write"
permissions for users to be able to edit data. This is true for all
versions of Access so I can't explain how users are able to edit data when
the host folder is apparently read only. I suspect that it is not. Anyone
else care to jump in on this one?

 

[Guus]

Hello Keith,
The database opens standard with a form, the user has to make some choices.
After choosing 'Submit' an Appendquery adds automatically the data on the
form into the table 'Loan' of the database.

In Office-2007 there happens nothing, yet.
Guus

 

[Albert D. Kallal]

All the users of our department are allowed to read/write files in the
folder "G:\General".

Are you talking about ms-access user level security, or rights setup by your
network?

Now the database has been moved to folder G:\Automation.
In this folder all the users are just allowed to READ files.

Again, if your talking about the network system, and NOT ms-accss user level
society, then what ms-access does have ZERO ZERO ZERO bearing here. If those
files are read only to all users, then they will REMAIN read only to those
users. NOTHING IN MS-ACCESS WILL CHANGE THIS FACT. Any user that needs to
update files in that directory MUST HAVE read + write permissions at the
network level (end of story). We are taking about a plane Jane windows file
here. If you open an access files, excel file, power-point file as read only
by the network, then it will REMAIN read only. If you open a file that your
read + write permissions, then you have read + write permissions (but, you
not be able to modify any other file that remains read only).

Adminstrator has setup the rights for 'Lending.mdb' specific to
read/write.

Again, are you talking about ms-access ULS, or your network permissions?

Office-2007 seems to handle different with read/write rights.
What's usefull to change, so everyone using Office-2007 can still use
'Lending.mdb'?

I not aware of any changes in ms-access 2007 in this regards. if you are
using ULS, then ensure that the access 2007 users are joined to the same
ms-access "mdw" workgroup file.

You should however keep in mind that if the 1st user that opens the file
opens it without network permissions (at the network level NOT ULS in
ms-access), then a locking file in that directory is NOT created and
ADDITIONAL USERS WITH READ + WRITE persimmons will be forced to open that
file as read only since the first user into that file was a read only user
(and the locking file can NOT be created - if this locking file cannot be
created, then all users are forced to read only - this read only issue only
applies to network security, NOT ms-access ULS).

So, clear up the issue if you using ULS (ms-access security) or your network
security, or in fact using both!!