Security created in all Access databases

[Guest]

Hi all,

I add security to a database using the security wizard. After that, all
other Access databases from other folders in my computer also has the same
security; the same users and groups. When I create a new blank database it
also has the same security and ask me to logon before even created it.
How can I remove this security?

Appreciated your help in advance.

Thank you

 

[Rick Brandt]

Hi all,

I add security to a database using the security wizard. After that,
all other Access databases from other folders in my computer also has
the same security; the same users and groups. When I create a new
blank database it also has the same security and ask me to logon
before even created it.
How can I remove this security?

Appreciated your help in advance.

Thank you

Access security is not "attached" to a particular file. It is applied to the
session of Access. When you open Access you are always using a workgroup (MDW)
file. If you don't specify one with a command line argument then your default
one is used. If your default workgroup has a password on the Admin user then
you are required to log in. Since users and groups are stored in the workgroup
file, you will see the same ones in all files as long as you use the same
workgroup.

So...security is *always* in affect in *all* Access files. What is different in
a secured file is that you use a workgroup file that requires a login (like
yours) and you assign permissions to objects and to the database itself in the
MDB file. While you are being required to login (by your workgroup), your other
files are not really secured because they do not have any restrictions on what
users and groups can use which objects.

What most people do is NOT change their default workgroup, but leave it set to
the System.MDW that does not require a login. Then for their secured files they
build a special shortcut that opens Access, specifies a non-default workgroup
(which requires a login), and specifies the secured file to open. Then you just
use that shortcut for your secured file and opening Access for all your other
files is not affected.

 

[John Vinson]

Hi all,

I add security to a database using the security wizard. After that, all
other Access databases from other folders in my computer also has the same
security; the same users and groups. When I create a new blank database it
also has the same security and ask me to logon before even created it.
How can I remove this security?

Appreciated your help in advance.

Thank you

The usernames and passwords for Access security are stored in a
database with a .MDW extension, called a "workgroup security" file.
The default is SYSTEM.MDW, ususally stored in C:\Windows\System32\
(but could be anywhere). If you change the usernames, passwords, etc.
in this file, and continue to use it, you'll get this happening.

Normally one would create a NEW MDW file specific for each Access
application, and either use Tools... Security... Workgroup Manger to
join it as needed, or use a Shortcut to open your database using the
/wrkgrp command line switch.

I'd REALLY recommend that you get a copy of the Microsoft Access 2000
Security FAQ:

http://support.microsoft.com/kb/207793/en-us

It applies to all current versions. Read it *carefully*. Put it under
your pillow and sleep on it. Read it carefully, AGAIN. Follow its
instructions scrupulously. It's easy to do security wrong, and the
security wizard is *not* the best authority on the subject!


John W. Vinson[MVP]

 

[David W. Fenton]

I add security to a database using the security wizard. After
that, all other Access databases from other folders in my computer
also has the same security; the same users and groups. When I
create a new blank database it also has the same security and ask
me to logon before even created it. How can I remove this
security?

There are two levels to user-level security:

1. the users and groups, stored in a workgroup file.

2. the permissions applied for those users and groups to a
particular MDB.

You haven't done #2 on any of the other databases, so security has
*not* been applied to them. All you're getting is the logon prompt,
necessitated by setting up #1. Even if you changed the admin
password back to blank, you'd still be logging in behind the scenes
as admin. So, the user logon is *always* in effect no matter what --
you just don't always see the logon prompt.