If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Read Only permission to folder where database resides
We have an Access database stored in a network folder, we then have a number
of users with full permissions to this folder and some users with read-only permissions. At present a user with read-only permissions only seems to be able to open the database when no-one else has it open. If they do manage to open it (i.e. no-one else in it at time) then it locks the file and non of the other users can access it. If the file is already in use when a read-only user tries to open it they get an Access error message "Can not Lock File" Anyone any ideas. Weve tried the database using Access 2000 and Access 2003. TIA Ally. |
#2
|
|||
|
|||
Ally H. wrote:
We have an Access database stored in a network folder, we then have a number of users with full permissions to this folder and some users with read-only permissions. At present a user with read-only permissions only seems to be able to open the database when no-one else has it open. If they do manage to open it (i.e. no-one else in it at time) then it locks the file and non of the other users can access it. If the file is already in use when a read-only user tries to open it they get an Access error message "Can not Lock File" Anyone any ideas. Weve tried the database using Access 2000 and Access 2003. TIA Ally. For things to work well, they need read, write, create and delete access. BTW is that a back-end database with front-end databases on the user's machines? If not, I suggest you consider splitting the database so you have that arrangement. It tends to work much safer and generally faster. -- Joseph E. Meehan 26 + 6 = 1 It's Irish Math |
#3
|
|||
|
|||
if the user can't create the .ldb file the database will
be opened in exclusive mode you will need to give them create/read/write/delete/change permission. -----Original Message----- We have an Access database stored in a network folder, we then have a number of users with full permissions to this folder and some users with read-only permissions. At present a user with read-only permissions only seems to be able to open the database when no-one else has it open. If they do manage to open it (i.e. no-one else in it at time) then it locks the file and non of the other users can access it. If the file is already in use when a read-only user tries to open it they get an Access error message "Can not Lock File" Anyone any ideas. Weve tried the database using Access 2000 and Access 2003. TIA Ally. . |
#4
|
|||
|
|||
What's the best way of going about making the data read-only for specific
users? I do usually split the front end from the back, but not in this case as it started out as a single user database but seems to have grown. Ally. "Joseph Meehan" wrote: Ally H. wrote: We have an Access database stored in a network folder, we then have a number of users with full permissions to this folder and some users with read-only permissions. At present a user with read-only permissions only seems to be able to open the database when no-one else has it open. If they do manage to open it (i.e. no-one else in it at time) then it locks the file and non of the other users can access it. If the file is already in use when a read-only user tries to open it they get an Access error message "Can not Lock File" Anyone any ideas. Weve tried the database using Access 2000 and Access 2003. TIA Ally. For things to work well, they need read, write, create and delete access. BTW is that a back-end database with front-end databases on the user's machines? If not, I suggest you consider splitting the database so you have that arrangement. It tends to work much safer and generally faster. -- Joseph E. Meehan 26 + 6 = 1 It's Irish Math |
#5
|
|||
|
|||
Ally H. wrote:
What's the best way of going about making the data read-only for specific users? The best way is user level security. Learning to use it is a very steep learning curve, but it is a great tool. Easy for the user and you, once YOU learn your part. The user does not need to do much. I suggest you start by reading http://support.microsoft.com/default.aspx?scid=kb;[LN];207793 Access security is a great feature, but it is, by nature a complex product with a very steep learning curve. Properly used it offers very safe versatile protection and control. However a simple mistake can lock everyone including God out. Practice on some copies to make sure you know what you are doing. The alternative is Access password protection. It is much less secure and less versatile, but it does work. For that the built in help file works fine. However I do recommend making a copy of the database before you start messing with it anyway. I do usually split the front end from the back, but not in this case as it started out as a single user database but seems to have grown. Yea, I know how that goes. User level security can work either way. Ally. "Joseph Meehan" wrote: Ally H. wrote: We have an Access database stored in a network folder, we then have a number of users with full permissions to this folder and some users with read-only permissions. At present a user with read-only permissions only seems to be able to open the database when no-one else has it open. If they do manage to open it (i.e. no-one else in it at time) then it locks the file and non of the other users can access it. If the file is already in use when a read-only user tries to open it they get an Access error message "Can not Lock File" Anyone any ideas. Weve tried the database using Access 2000 and Access 2003. TIA Ally. For things to work well, they need read, write, create and delete access. BTW is that a back-end database with front-end databases on the user's machines? If not, I suggest you consider splitting the database so you have that arrangement. It tends to work much safer and generally faster. -- Joseph E. Meehan 26 + 6 = 1 It's Irish Math -- Joseph E. Meehan 26 + 6 = 1 It's Irish Math |
#6
|
|||
|
|||
I'll check out that link thanks for your help.
"Joseph Meehan" wrote: Ally H. wrote: What's the best way of going about making the data read-only for specific users? The best way is user level security. Learning to use it is a very steep learning curve, but it is a great tool. Easy for the user and you, once YOU learn your part. The user does not need to do much. I suggest you start by reading http://support.microsoft.com/default.aspx?scid=kb;[LN];207793 Access security is a great feature, but it is, by nature a complex product with a very steep learning curve. Properly used it offers very safe versatile protection and control. However a simple mistake can lock everyone including God out. Practice on some copies to make sure you know what you are doing. The alternative is Access password protection. It is much less secure and less versatile, but it does work. For that the built in help file works fine. However I do recommend making a copy of the database before you start messing with it anyway. I do usually split the front end from the back, but not in this case as it started out as a single user database but seems to have grown. Yea, I know how that goes. User level security can work either way. Ally. "Joseph Meehan" wrote: Ally H. wrote: We have an Access database stored in a network folder, we then have a number of users with full permissions to this folder and some users with read-only permissions. At present a user with read-only permissions only seems to be able to open the database when no-one else has it open. If they do manage to open it (i.e. no-one else in it at time) then it locks the file and non of the other users can access it. If the file is already in use when a read-only user tries to open it they get an Access error message "Can not Lock File" Anyone any ideas. Weve tried the database using Access 2000 and Access 2003. TIA Ally. For things to work well, they need read, write, create and delete access. BTW is that a back-end database with front-end databases on the user's machines? If not, I suggest you consider splitting the database so you have that arrangement. It tends to work much safer and generally faster. -- Joseph E. Meehan 26 + 6 = 1 It's Irish Math -- Joseph E. Meehan 26 + 6 = 1 It's Irish Math |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
database is read only | Jose8 | General Discussion | 1 | August 14th, 2004 05:11 AM |
Error: Documentor, Record(s) cannot be read; no read permission on AccessLayout | Sid | General Discussion | 0 | August 5th, 2004 02:33 PM |
Read Only Folder | cwt | General Discussion | 1 | June 16th, 2004 04:14 PM |
Code to read a cell from every workbook in a folder | dovrox | General Discussion | 1 | June 16th, 2004 12:45 AM |
DATABASE SQL staments | ediaz | Mailmerge | 2 | May 5th, 2004 07:20 AM |