secured db still opens with system.mdw

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have followed the directions exactly from the website below and was able
to secure the database.
http://www.jmwild.com/security02.htm

However, it reccommends after db is secure, to open Access and re-join the
system.mdw. I did this and now...
When I use the shortcut, the security works great but when I click on the
..mdb the database opens without security.

What did I do wrong??
 
deb said:
I have followed the directions exactly from the website below and was
able to secure the database.
http://www.jmwild.com/security02.htm

However, it reccommends after db is secure, to open Access and
re-join the system.mdw. I did this and now...
When I use the shortcut, the security works great but when I click on
the .mdb the database opens without security.

What did I do wrong??
Click to expand...

You missed a step.

Whenever you open a file with a workgroup that does not prompt you for a
user name and password then you are silently logged in as user 'Admin'
member of group 'Users'. In a properly secured file neither of those
entities should be able to open the file.

If you believe you have removed all permissions from 'Admin' and 'Users'
then check the owner of the database. If you left 'Admin' as owner then
that is the problem. Owners have rights above and beyond their permission
settings.
 
I followed the directions step by step. It is evident that I did something
wrong...

How do I check to see who the owner is?
I need a little more information on how to troubleshoot this.
Your help is much appreciated.
 
To explain a bit further...

The test database that I have built to learn security was used with the
Security Step by Step by Joan Wild. It is using the test.mdw that was
created.

Now every db I open is using this security. I did not want this.

The last part of the tutorial said to open Access (without opening a db) and
switch back to system.mdw. When I did this I can open all mdb's with out
having to log in. Including the test db. The only way to log into the test
db sucured is via the shortcut.

It seems that either all or none of the mdb's have log in security, unless
the shortcut is used. I am so confused.
 
I checked what you said...
Step 3 creates a new workgroup (Access is open but not a db)
Step 7 creates a new user
Step 8 adds admin group to the new user
Step 9 removes the admin user from the admins group
Step 11 Closes Access
Step 12 opens the unsecured db
Step 14 opens the security wizard
Step24 choose no to user group having permissions

The missing steps were followed but not listed above. I listed the steps
that show that new user was added to admin group and admin user was removed
from admin group. Security wizard was used to remove permissions from "user"
user.

but if the mdb is opended it is unsecure. The only sercurity is via shortcut.

Someone PLEASE help me!!!

Once this security is setup. It said to go back to Access(without db open)
and change back to system.mdw.

Now the db is secure only if the shortcut is used. Not Good!!!
 
deb said:
I followed the directions step by step. It is evident that I did
something wrong...

How do I check to see who the owner is?
I need a little more information on how to troubleshoot this.
Your help is much appreciated.
Click to expand...

From the menu...

Tools
Security
User and Group Permissions

In the resulting form there should be a list of Object Types. From that
list choose "Database". It should be listed at the very top. Once that is
selected the owner of the datbase object will be shown. It should be the
new user that you created and added to the Admnins group, NOT the user
'Admin'.

You can also use that form to review what users and groups have permissions
to what objects.
 
To explain a bit further...

The test database that I have built to learn security was used with the
Security Step by Step by Joan Wild. It is using the test.mdw that was
created.

Now every db I open is using this security. I did not want this.

The last part of the tutorial said to open Access (without opening a db) and
switch back to system.mdw. When I did this I can open all mdb's with out
having to log in. Including the test db. The only way to log into the test
db sucured is via the shortcut.

It seems that either all or none of the mdb's have log in security, unless
the shortcut is used. I am so confused.
Click to expand...

Access always uses workgroup security, even right out of the box. In a default installation, you are actually being
logged in as the Admin user, with no password, and you're using the system.mdw workgroup file. There is one user in the
system.mdw file (Admin) and that user is a member of the Admins and Users group. That user is also the owner of all
objects, including any databases, that are built.

So ULS consists of two files: the workgroup file, and the database itself. The workgroup file stores Users, Groups, and
User-Group memberships, as well as passwords. The database stores Permissions (i.e. User/Group permissions for the
various objects in the database). When you login, the workgroup file "authenticates" you, then basically passes this
info to the database; the database then uses this information to determine the permission levels for that user for the
various obejcts in the database.

In your case, you're probably still "joined" to your test.mdw file ... you can check this by opening Access (don't open
a database) and clicking Tools - Database Security - Workgroup Administrator. If you are joined to test.mdw, then find
and rejoin the default system.mdw file.

If you can login to your database while joined to system.mdw, then you've not secured it properly. It's easy to miss a
step, so go through the checklist on Joan's site step-by-step, and check off each one as you do it. There are several
steps that, if missed, will cause the troubles you're seeing.

I'd also encourage you to read Jack MacDonald's excellent writeup on ULS; Joan has a link to it on her site.


Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
 
Deb,
I know this is pretty low-level, but I don't think I recall you mentioning
it in your notes, and it comes at the end Joan's security step-by-step: Have
you checked your shortcut to make sure that it points to the correct security
workgroup?
I could see this as a simple thing to miss that would drive you nuts.
JAT.
 
NO PROBLEMS, CONTACT ME...
--
PACALA JAN [ACCESS DEVELOPER]
SEND 10$ TO...
ACCOUNT:
SK31 1100 0000 0026 1674 0428
SwiftCode: TATRSKBX
Tatra banka as,Hodzovo nam.3, 811 06 Bratislava
(e-mail address removed)
SKYPE: PACALA.BA1
 
These newsgroups are for the FREE exchange of ideas, information, and
assistance. This is absolutely NOT the place to troll for business: such
postings are not welcome, and they make such a bad impression that it can
only hurt your reputation in the Access community.

If you want to post actual advice and assistance here in the newsgroups for
all to benefit from, or post questions of your own, then your participation
will be welcomed.

--
Doug Steele, Microsoft Access MVP

(no private e-mails, please)


NO PROBLEMS, CONTACT ME...
--
PACALA JAN [ACCESS DEVELOPER]
SEND 10$ TO...
ACCOUNT:
SK31 1100 0000 0026 1674 0428
SwiftCode: TATRSKBX
Tatra banka as,Hodzovo nam.3, 811 06 Bratislava
(e-mail address removed)
SKYPE: PACALA.BA1


deb said:
I have followed the directions exactly from the website below and was
able
to secure the database.
http://www.jmwild.com/security02.htm

However, it reccommends after db is secure, to open Access and re-join
the
system.mdw. I did this and now...
When I use the shortcut, the security works great but when I click on the
.mdb the database opens without security.

What did I do wrong??
Click to expand...
Click to expand...
 
Back
Top