Microsoft Access Security

I HAVE CREATED A SECURITY DATABASE USING A NEW WORKGROUP FILE WITH A NEW MDW FILE NAME. THE DATABASE ITSELF CONTAINS SEVERAL GROUPS OF USERS AND SEVERAL USERS. THE DATABASE WORKS AS DESIGNED.
THE PROBLEMS IS IF I OPEN THIS DATABASE USING THE SYSTEM.MDW FILE, THE DATABASE OPENS AND GIVE ME COMPLETE ACCESS TO EVERYTHING.

CAN ANYONE EXPLAIN WHAT IS HAPPENING.

ANY HELP WILL BE APPRECIATED

THANKING YOU IN ADVANCE

JOSEPH FORDDid you give the user Admin a password?

Did you join to the workgroup?|||Originally posted by Brett Kaiser
Did you give the user Admin a password?

Did you join to the workgroup?
I gave the admin a password and then created a new administer with a different name.

When I open the database with the workgroup I created it works fine.
but when I open the database with the system.mdw workgroup it allow me to enter the database. which should not be. I am missing something.

Thanks|||And it doesn't ask you for a password, right?|||Originally posted by Brett Kaiser
And it doesn't ask you for a password, right?

Yes that is correct. The following information I found in Q/A section. What do you make of this.
10. Additionally, you may need manually to remove the Open/Run permission from the database container for the Users group through the security menus or through code. This will prevent someone from opening the database by using another workgroup information file or the default System.mda/mdw. In Microsoft Access 97, the User Level Security Wizard is supposed to remove the Open/Run database permissions for the Users group, but fails to do so. The Access 2000 Security Wizard removes permissions to the point where they are not visible on the security menus, but testing has revealed that in Access 2000 it is possible to open a database by using the default workgroup information file regardless of the menu settings. The cure for both versions of Access is to create a new, empty database while logged on as a member of the Admins group and import all of the objects from the secured database. You should take this step before spending too much time securing objects because Access considers imported objects to be new and loses the permission information that was stored in the source database.|||Yeah..it's a toy...

Don't use the default workgroup...

But you said you removed all of the permissions from Admin (that's what it's opening with), but it doesn't seem to be the case...

You sure your removed Admin from the Admin group?

And made sure it had no permissions?|||Originally posted by Brett Kaiser
Yeah..it's a toy...

Don't use the default workgroup...

But you said you removed all of the permissions from Admin (that's what it's opening with), but it doesn't seem to be the case...

You sure your removed Admin from the Admin group?

And made sure it had no permissions?

I think I have but could be wrong. I have attached a file that I would appreciate your looking at to see if you can see the problelm.

Thanks for your help

Joe Ford|||I think you forgot the attachment...|||Originally posted by Brett Kaiser
I think you forgot the attachment...

Your are right. I have attached it now. Please forgive my senior memo.|||OK,

How about what he permissions are fopr the user group...|||Originally posted by Brett Kaiser
OK,

How about what he permissions are fopr the user group...

ALL USERS ARE PART OF THE USER GROUP AND THAT GROUP HAS NO PERMISSION AT ALL INCLUDING ADMIN.|||Yeah...I figured as much...

Who is the owner of all the objects...Where they all originally created by Admin?|||Originally posted by Brett Kaiser
Yeah...I figured as much...

Who is the owner of all the objects...Where they all originally created by Admin?

Owner is Poweradmin see attached|||What about the other objects (like tables, macros, ect)...don't know if dbowner does it...I think it should...

who owns them?|||Originally posted by Brett Kaiser
What about the other objects (like tables, macros, ect)...don't know if dbowner does it...I think it should...

who owns them?

they are all owned by poweradmin|||Make sure u encrypt ur database using workgroup information file

Also inform u are whitout knowing that even if u create particular
security file for an access database .. .Users group which is default to any *.mdw file will be created and access won't allow u to delete it ...

however make sure you didn't grant any permission to this group

regards ...