Database in readonly mode with FE/BE setup

[NuBie via AccessMonster.com]

Database is an FE/BE setup. However we have a scenario here that when the
database is opened by someone everybody gets locked out. Locked out means
they can open the forms on the DB but couldn't add/edit records.The message
says "....the database has been opened read only...".

That one person was the former owner/developer of the database and was
recently moved to another department. He has nothing to do with the daily
operations with regards to the DB, since he's on another Dept. BUT, he feels
he owns the database he created (it's a personal thing), so he opens it from
time to time, and that gets everybody "locked out". Below is the Folder
Security Settings on the network where the BE resides.

File/Folder Settings:
Everybody/Former Owner : Read&Execute; Read; List Folder Contents
Current Users : Read&Execute; Modify ;Write ;Read ;List
Folder Contents

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? Or is there any clarification why this is happening and any suggestion
for work around to prevent this.

 

[Gina Whipp]

NuBie,

Are they all sharing the same Front-End OR does everyone have their own copy
of the front end?

--
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]

They have their own copy of Front-end.

NuBie,

Are they all sharing the same Front-End OR does everyone have their own copy
of the front end?

Database is an FE/BE setup. However we have a scenario here that when the
database is opened by someone everybody gets locked out. Locked out means

[quoted text clipped - 23 lines]

DB? Or is there any clarification why this is happening and any suggestion
for work around to prevent this.

 

[Gina Whipp]

NuBie,

Then it sounds like the original database owner is opening the database in
Exclusive mode WHICH is an internal employee issue. I am at a loss as to
how to stop this individual fro doing this aside from denying them access
altogether. I would suggest taking that up with management.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

They have their own copy of Front-end.

NuBie,

Are they all sharing the same Front-End OR does everyone have their own
copy
of the front end?

Database is an FE/BE setup. However we have a scenario here that when
the
database is opened by someone everybody gets locked out. Locked out
means

[quoted text clipped - 23 lines]

DB? Or is there any clarification why this is happening and any
suggestion
for work around to prevent this.

 

[NuBie via AccessMonster.com]

well, actually he's opening it via the front-end MDE.

I would suggest taking that up with management.

That's what I'm thinking. I'll raise this issue next staff meeting...

Thank you Gina for your time!

NuBie,

Then it sounds like the original database owner is opening the database in
Exclusive mode WHICH is an internal employee issue. I am at a loss as to
how to stop this individual fro doing this aside from denying them access
altogether. I would suggest taking that up with management.

They have their own copy of Front-end.

[quoted text clipped - 12 lines]

 

[Gina Whipp]

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.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

well, actually he's opening it via the front-end MDE.

I would suggest taking that up with management.

That's what I'm thinking. I'll raise this issue next staff meeting...

Thank you Gina for your time!

NuBie,

Then it sounds like the original database owner is opening the database in
Exclusive mode WHICH is an internal employee issue. I am at a loss as to
how to stop this individual fro doing this aside from denying them access
altogether. I would suggest taking that up with management.

They have their own copy of Front-end.

[quoted text clipped - 12 lines]

suggestion
for work around to prevent this.

 

[NuBie via AccessMonster.com]

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

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]

 

[Gina Whipp]

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

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

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.

 

[Tom van Stiphout]

On Wed, 4 Nov 2009 17:51:57 -0500, "Gina Whipp"

Hi Gina,
Do you know of a way to test if a user opened the app Exclusively? If
there was such a test, the OP could look for that, bitterly complain,
and close the app.

-Tom.
Microsoft Access MVP

 

[Gina Whipp]

Tom,

I wish I did know of a way!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Tom van Stiphout]

On Thu, 5 Nov 2009 00:36:32 -0500, "Gina Whipp"

I added a request on Microsoft Connect:
https://connect.microsoft.com/office/feedback/ViewFeedback.aspx?FeedbackID=508480

-Tom.
Microsoft Access MVP

 

[Gina Whipp]

Tom,

You know that would be a great feature! Thanks!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

 

[Joan Wild]

Nothing is getting inherited. When a user opens a mdb or mde, an
associated ldb file is created in the same folder. In your case, since
this user does not have create permission on the folder, they are not
able to create the ldb, and therefore the mdb is opened exclusively.

You need to ensure that one of the Current Users opens the mdb first,
then everyone will play fine.


Joan Wild

 

[NuBie via AccessMonster.com]

In your case, since this user does not have create permission on the folder, they are not able to create the ldb, and therefore the mdb is opened exclusively.

I think this explain why.

Thank you Gina,Tom, Joan and the Access Monster Group.
MORE POWER!!!

Nothing is getting inherited. When a user opens a mdb or mde, an
associated ldb file is created in the same folder. In your case, since
this user does not have create permission on the folder, they are not
able to create the ldb, and therefore the mdb is opened exclusively.

You need to ensure that one of the Current Users opens the mdb first,
then everyone will play fine.

Joan Wild

Gina,

[quoted text clipped - 10 lines]

Thank you

 

[Gina Whipp]

THANK YOU Joan... I guess we missed the forest for the trees!

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index_files/TipList.htm

In your case, since this user does not have create permission on the
folder, they are not able to create the ldb, and therefore the mdb is
opened exclusively.

I think this explain why.

Thank you Gina,Tom, Joan and the Access Monster Group.
MORE POWER!!!

Nothing is getting inherited. When a user opens a mdb or mde, an
associated ldb file is created in the same folder. In your case, since
this user does not have create permission on the folder, they are not
able to create the ldb, and therefore the mdb is opened exclusively.

You need to ensure that one of the Current Users opens the mdb first,
then everyone will play fine.

Joan Wild

Gina,

[quoted text clipped - 10 lines]

Thank you