Re: secured db, yet insecure with alternate worgroup file..
nycdon wrote:
> I did check that wizard converted all objects' ownerships.[snip]
Did you check ownership of the "Database" object? That is usually what will be
left as "Admin" by people setting up security who don't know what they're doing.
If a user account "owns" the database then they can open the file regardless of
any other permission settings.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com
.
Relevant Pages
- Re: Sorting out security
... > MS Access security. ... > created a new workgroup, added a password for the Admin role, added ... > remote logins to a secured database. ... The location of the current workgroup file is recorded in the ...
(microsoft.public.access.security) - Sorting out security
... MS Access security. ... created a new workgroup, added a password for the Admin role, added groups, ... user IDs and passwords for users and allocated permissions on the ... remote logins to a secured database. ...
(microsoft.public.access.security) - Re: Problems setting up access security
... So, for some reason, it seems that Access security does not work when Access ... try to go directly into the database, they have to use the shortcut and log ... "Joan Wild" wrote: ... The Admin user still owns the database object. ...
(microsoft.public.access.security) - Re: Sorting out security
... There is a link to it on the Security page of my website. ... > files and remote logins to a secured database. ... different name for the secure workgroup file. ... If the Admin user has no password then every user is ...
(microsoft.public.access.security) - RE: How to remove user level security
... It sounds like you did not secure your database but you just forget what ... the passwords are for the Admin account and the account that has Admins ... Reopen Microsoft Access and try opening one of your databases. ... The security wizard creates a ...
(microsoft.public.access.security) |
|
