RE: Mystery security group setting changes.

The .mdw file I use for this workgroup is called "share.mdw" and the default
mdw is called "system.mdw." Sometimes when there are updates, a few users'
computers get set back to the default system.mdw -- but I'm talking about
changes taking place in the workgroup file I created, share.mdw. Nothing has
ever changed, before, in the share.mdw file, even after updates -- but now,
suddenly the Admin user rejoined the ADMINS group within share.mdw. I don't
think installing updates can change the contents of the mdw file I created
(share.mdw), right? This share.mdw file has been in use for over 2 years (I
created it), and this is the first time I've seen the Admin user mysteriously
rejoin the ADMINS group. There are only two users who are part of the
ADMINS group: myself and the IT manager. I am the one who does all the
development, security, etc., and the manager knows Access, but doesn't really
do anything with the data system. But yesterday, I found the Admin user also
in this ADMINS group -- and was shocked to see it there -- and this is all in
the Workgroup called share.mdw. So I'm not talking about access reverting
back to the default system.mdw file, but rather a change occuring within the
share.mdw file I created as a security workgroup for our data system. Does
this make better sense?

"Joan Wild" wrote:

Updates can sometimes set your default mdw back to factory i.e. back to
system.mdw that ships with Access. And in that mdw Admin is a member of the
Users Group. Are you certain of the mdw file you are using? You can double
check by opening Access, hitting Ctrl-G and typing DbEngine.SystemDb

--
Joan Wild
Microsoft Access MVP


"eagle" wrote:

When I first set up user-level security, I removed Admin user from Admins
group, and removed all permissions from Admin user. I also removed all
permissions from Users group. Today (2 years later) I noticed Admin user was
back in the ADMINS group. How can this happen? I mentioned this to the top
IT person here, and she says that when microsoft updates and service packs
are installed, it can cause stuff to go back to default settings. This
doesn't make sense to me because the workgroup file is a separate file (like
a doc) and that is where the changes were made. Can updates and service pack
installs make changes to a workgroup file like that? Even if, wouldn't it
reset all the groups and users I created back to nothing?

Anyway, if the Admin user were successfully removed from ADMINS group, HOW
could it get back in there? This is what I need to know. I am the database
developer/administrator/support/everything. Thanks. :-)
.

Relevant Pages

  • Re: User able to bypass security
    ... Isn't the Admin User always in the Admins group in the default Workgroup ...
    (microsoft.public.access.security)
  • Re: User able to bypass security
    ... It had not even occured to me that the "Admin user would still be in the ... create a new "Admins" group! ... You can remove admin from the Admins group in one workgroup ...
    (microsoft.public.access.security)
  • Re: Workgroup Question
    ... How can I delete a workgroup all together. ... it isn't necessary to remove the permissions from the Admins Group ... Admin user has a pwd in place. ... Permissions are stored in the database file itself. ...
    (microsoft.public.access.security)
  • Re: Always asked to login, and I cant!
    ... This is known as a "secure" workgroup. ... The default Admin user most definitely has a password, ... if you want to open or create a database file. ...
    (microsoft.public.access.security)
  • Re: Security confusion
    ... I still believe though that you should import all objects into a new database container since ... >> I've never even heard it was possible to do this via the Immediate Window. ... but did you remove the Admin USER from the Admins GROUP? ...
    (microsoft.public.access.security)
Loading