Permission problems

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Version Access XP. Sharing db with Lan no server, no split database. 6
users with different permissions. It has been working fine until SP3 is
updated.

One user has the permissions of Backup Operators and Update Data Users.
This user gets an error msg "You do not have exclusive right to access this
database,....". If the Full permission is added, then the error msg will not
come out.

Another work around is to open the same db from the recent file rather than
clicking on the shortcut from Desktop, the error msg won't appear. There
seems to have some conflicts somewhere. I can't figure out the difference
between the two ways of opening the db while both link to the same path.
 
You're talking about Windows permissions, not Acess ones - right?

Every user of an Access database must have read/write/delete/execute
permission to the folder where the database lives. You can easily find
the reason for this by googling this group on suitable keywords.

Also, it is generally accepted that sharing a single (non-split)
database is likely to lead to corruption. Do you have any particular
reason for not splitting it?

HTH,
TC
 
I am talking about the Access permissions. The Windows permissions is set to
shared with full permissions.
All users permissions are set from the Tools\Security\User & group
permissions. Is there somewhere else I should set the
read/write/delete/execute permission?

I am not quite sure how better the splitting will work. The non splitting
has been working well before this problem.
 
kenlo said:
I am talking about the Access permissions. The Windows permissions is set to
shared with full permissions.
Click to expand...

But there are no MS Access permissions called "Backup Operators",
"Update Data Users", or "Full". Are you sure that those are not the
names of Access Groups? Are you adding users to (and removing them
from), Access Groups of those three names?
This user gets an error msg "You do not have exclusive right to access this
database,....".
Click to expand...

This usually means that the database has been started by a *Windows*
user who does not have full read/write/execute/delete *Windows*
permissions to the folder where the MDB file lives.
If the Full permission is added, then the error msg will not
come out.
Click to expand...

There is no "Full permission" in MS Access. There could be an Access
Group called "Full", but I can't see how that error could be dependent
on what Access Group the user belonged to.
All users permissions are set from the Tools\Security\User & group
permissions. Is there somewhere else I should set the
read/write/delete/execute permission?
Click to expand...

No, I was referring to Windows permissions, not Access ones. I'm not
sure where you set them in Windows, cos I have never actually done it
myself.
I am not quite sure how better the splitting will work. The non splitting
has been working well before this problem.
Click to expand...

Fine if it works! But it is commonly believed to increase the chances
of data corruption in your database. There are some other significant
advantages of the split approach, but maybe those do not apply to your
particular situation. Google on "FE/BE structure", "split database" or
similar for more information.

HTH,
TC
 
TC said:
But there are no MS Access permissions called "Backup Operators",
"Update Data Users", or "Full". Are you sure that those are not the
names of Access Groups? Are you adding users to (and removing them
from), Access Groups of those three names?
Click to expand...

Those are Access security groups that the wizard offers.
This usually means that the database has been started by a *Windows*
user who does not have full read/write/execute/delete *Windows*
permissions to the folder where the MDB file lives.
Click to expand...

There are other possibilities, especially if the mdb isn't split. Kenlo
what are the users doing when the error message comes up?
 
Back
Top