New security

[Jonathan]

Hello all,

I thought I understood setting up security but I'm having a problem. I'm
using Access 2002. Here's the scenario:

I start with an unsecured database and I create a new workgroup file.

I open the database with an Access shortcut using the /wrkgrp flag pointing
to the new mdw file.

I add a new user (Admin102) to the Admins group.

I put a password on the Admin user and remove it from the Admins group

I exit Access and open it with the shortcut.

I log in with Admin102 (which is in the Admins group) with no password.

I set a password for Admin102



From Admin102 I can't open any objects either to run or design. I thought
since Admin102 is in the Admins group it would have complete authority for
all changes.



What am I not getting?



Second question:

This is actually a split database with all tables linked from a separate db.
How do I secure the database with the tables to be consistent with the one
holding the forms, etc? Is this related to my above problem?





Thanks in advance

Jonathan

 

[Tony_VBACoder]

Did you follow the exact steps outlined in the "MS Access
Security FAQ"? Try looking at these articles:

http://download.microsoft.com/download/access97/faq1/1/WIN9
8/EN-US/Secfaq.exe

Understanding the role of workgroup information files in
Access security:
http://support.microsoft.com/default.aspx?scid=kb;en-
us;305542&Product=acc2002

http://support.microsoft.com/default.aspx?kbid=254372

 

[Jonathan]

Yes I followed all the steps. My Admin102 account has no permissions. I've
tried this multiple times (I have an unsecured copy of the database backed
up) recreated a new mdw file each time.

Any ideas?
Jonathan

 

[Joan Wild]

Actually at this point, it should have full permissions because Admin102 is
a member of the Users Group, and the database is still not secured.

You should create a new mdb (while logged in as Admin102) and import all
objects from your unsecured mdb.
If it helps, you can follow the steps I've outlined at
www.jmwild.com/AccessSecurity.htm

You create a new mdb (while logged in as Admin102 using your secure mdw),
and import all objects from the backend. Then apply the security you wish,
ensuring you remove permissions for the Users Group and the Admin user.

 

[Jonathan]

Thank you. Can you explain why the following would happen:
I create a new workgroup file (TEST.mdw) and join it
I open up an unsecured database
I find I have NO access to any of the objects.
When I rejoin system.mdw I have rights to the entire database.

Thanks
Jonathan

 

[Joan Wild]

Thank you. Can you explain why the following would happen:
I create a new workgroup file (TEST.mdw) and join it
I open up an unsecured database
I find I have NO access to any of the objects.
When I rejoin system.mdw I have rights to the entire database.

No that makes no sense. A new workgroup file has the same Users Group and
Admin user that the system.mdw file has.

When you use the system.mdw and open the database, what users and groups are
listed in tools, security, accounts? Under tools, permissions, what user or
group is listed as the owner of the database object?