Re: Why Are "Permission Entries" changed

From: Ken Winters (kwinters_at_olympus.net)
Date: 03/09/05 

Date: Tue, 8 Mar 2005 19:31:28 -0800

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

Relevant Pages

  • Re: Why Are "Permission Entries" changed
    ... folder to hold the mdb with the permissions needed set on the folder ... >I am setting the permissions on the actual database file, ...
    (microsoft.public.win2000.security)
  • Re: ADODB Table Update proplem
    ... I suppose this is the problem with the permissions allowed for your folder ... containing the database file. ... the recordset ...
    (microsoft.public.vb.database)
  • Re: Access 2007 at Odds with Vista
    ... edit button or advanced button to check the user permissions. ... As you had put the file into Desktop folder, root directory of this folder is ... I omitted the piece on the trusted location. ... "owner" of the database file, ...
    (microsoft.public.access.modulesdaovba)
  • Re: AccessDB on a WebServer
    ... I checked and was told that the permissions are set to ... read/write/execute on both the folder and the database file. ... Now, as I see it, the Pubs.mdb database lives in a folder on the webserver ...
    (microsoft.public.dotnet.languages.vb)
  • Re: One works the other doesnt
    ... users of a database file need to be able to create, ... That means they need Modify permissions for the _folder_ ... So the connection for the first page could still be ... then the user is the IUSR_machinename account (or whatever ...
    (microsoft.public.inetserver.asp.db)