Re: Why Are "Permission Entries" changed
From: Roger Abell [MVP] (mvpNoSpam_at_asu.edu)
Date: 03/09/05
- Next message: MinNY: "Password expiration warning"
- Previous message: Ronald: "Missing IP address in Security Audit"
- In reply to: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Next in thread: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Reply: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Reply: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 8 Mar 2005 23:12:10 -0700
The answer, explaination, and work-around by defining a dedicated
folder to hold the mdb with the permissions needed set on the folder
are all correct.
-- Roger Abell Microsoft MVP (Windows Server System: Security) MCDBA, MCSE W2k3+W2k+Nt4 "Ken Winters" <kwinters@olympus.net> wrote in message news:112srgfmngp6b50@corp.supernews.com... >I am setting the permissions on the actual database file, but your answer >isn't the case (it was one of my first thoughts too). I can create a new >database in the same folder (which has "Everyone" on it's access list), >open, edit, and save that database repeatedly. "Everyone" remains on it's >access list. But as soon as I run the MS Access Repair/Compact utility it >removes "Everyone" (along with any other non-Administrator users) from the >access list. > > I agree that there's an underlying bug, but I don't have the opportunity > to deal with that. I'm simply trying to provide some end users with the > ability to repair/compact the database without making them also manually > add "Everyone" back to the access list. > > Thanks, > Ken > > "Tim" <Tim@NoSpam.com> wrote in message > news:d0lo7m$k2p$1@lust.ihug.co.nz... >> If you are setting the permissions on the actual database file then the >> answer is obvious. >> >> The compression routine works like follows (well, this is how it should >> work): >> >> MDB ==> Compressed MDB >> MDB ==> renamed temp file (.BAK usually) >> Compressed MDB ==> renamed to original MDB >> The reason for this convoluted approach is that the MDB file does not get >> deleted until there is a known good compressed file in existance - if the >> process fails, it just leaves the original MDB file in place. >> >> If you indicate you want to keep the backup (depends on the utility) then >> the .BAK stays and will have the permissions you have set. >> >> Since the new MDB was created from scratch during the first step, it >> inherits its permissions from the file store container it is in. >> >> The solution is simple: grant the permissions to the containing folder. >> If you are hesitent to do this because of what else is contained in the >> folder, then move the MDB file to a dedicated folder and set the >> permissions on it. >> >> Personally, I would raise this as a bug with the software vendors as NO >> software should require the EVERYONE group to have permissions to >> anything (IMHO). >> >> - Tim >> >> >> >> >> >> "Ken Winters" <kwinters@olympus.net> wrote in message >> news:112sjjknte15819@corp.supernews.com... >>>I have an application that requires username "Everyone" to be granted >>>permission for a MS Access database file. But everytime I run the MS >>>Access Repair/Compact tool (to eliminate database corruption and free up >>>space) username "Everyone" is removed from the "Permission Entries" list >>>for the database file. >>> >>> Why? And how can I configure the security on that database file so this >>> doesn't happen? >>> Thanks >>> >> >> > >
- Next message: MinNY: "Password expiration warning"
- Previous message: Ronald: "Missing IP address in Security Audit"
- In reply to: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Next in thread: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Reply: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Reply: Ken Winters: "Re: Why Are "Permission Entries" changed"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
