Re: Database in readonly mode with FE/BE setup
- From: "Gina Whipp" <NotInterested@xxxxxxxxxxxxx>
- Date: Wed, 4 Nov 2009 17:51:57 -0500
NuBie,
No, your assumption is incorrect. Regardless of the permissions you have
assigned to the folder if ANY user opens the database in Exclusive Mode
everyone would get the *Read Only* message. Users don't inherit permissions
from another User.
Think of it like this, I have two locks on the door. One lock requires a
key and the other one is just a dead bolt. I have given 5 Users the key to
one lock which is the only lock I use. But 1 of those Users goes in and
locks the top lock while inside. Well, nobody has a key to that lock,
because there isn't one, so they will never get in until that 1 User unlocks
the top lock. Now, because you have an .mde and no design changes can take
place there would be no reason to every go in and turn the bolt. HOWEVER,
there is no way I know of to remove that lock if the person has the full
version of Access installed.
You did not say what platform you were moving this application to BUT I
would say if it is Access then some steps might have to be taken to insure
this person does not continue to disrupt eveyone. Say putting the back-end
on an SQL Server. Then as long as everyone has there own front end there is
no way that person without FULL admin rights tot he Server can do this.
--
Gina Whipp
"I feel I have been denied critical, need to know, information!" - Tremors
II
http://www.regina-whipp.com/index_files/TipList.htm
"NuBie via AccessMonster.com" <u42912@uwe> wrote in message
news:9ea1243c75b9b@xxxxxx
Gina,
Is my assumption below correct ?
It seems that when the former owner who has R;R&E permission on the
folder,
when he opens the DB the folder permission is also inherited and applied
to
DB?
File/Folder Settings:
Everybody/Former Owner : Read&Execute; Read; List Folder Contents
Current Users : Read&Execute; Modify ;Write ;Read ;List
Folder Contents
Thank you
Gina Whipp wrote:
NuBie,
Just as a note... I did not realize it was an .mde. He has no reason to
open the .mde in exclusive mode because in that state he cannot make
changes
to it. I THOUGHT you were using an .mdb which would mean he could say I
am
making changes that is why I am locking everyone out. I don't want to
*get
anyone in trouble* but I am under the impression he is doing that just
because he can.
well, actually he's opening it via the front-end MDE.[quoted text clipped - 15 lines]
suggestion
for work around to prevent this.
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200911/1
.
- Follow-Ups:
- Re: Database in readonly mode with FE/BE setup
- From: Tom van Stiphout
- Re: Database in readonly mode with FE/BE setup
- References:
- Database in readonly mode with FE/BE setup
- From: NuBie via AccessMonster.com
- Re: Database in readonly mode with FE/BE setup
- From: Gina Whipp
- Re: Database in readonly mode with FE/BE setup
- From: NuBie via AccessMonster.com
- Re: Database in readonly mode with FE/BE setup
- From: Gina Whipp
- Re: Database in readonly mode with FE/BE setup
- From: NuBie via AccessMonster.com
- Re: Database in readonly mode with FE/BE setup
- From: Gina Whipp
- Re: Database in readonly mode with FE/BE setup
- From: NuBie via AccessMonster.com
- Database in readonly mode with FE/BE setup
- Prev by Date: Re: Database in readonly mode with FE/BE setup
- Next by Date: Re: Database in readonly mode with FE/BE setup
- Previous by thread: Re: Database in readonly mode with FE/BE setup
- Next by thread: Re: Database in readonly mode with FE/BE setup
- Index(es):
Relevant Pages
|