Securing a database with a current workgroup file

[Jacques Latoison]

How does one secure a database using a current workgroup file. I have
several databases that need user level security.

1) I created the first database and secured it using the wizard.
2) The first one cannot be open without the workgroup file (which is what
I'm looking for).
3) I make any other databases and they can still be open without logging in.
4) The Wizard won't let me use a current workgroup file.
5) I can't change the change the Database owner from Admin (but I have
changed every other object in the database).

I assume number 5 is the problem, so how do I get around this and secure the
database. It says its encoded, but anyone can open the thing without
credentials.

 

[White Bilky]

How does one secure a database using a current workgroup file. I have
several databases that need user level security.

1) I created the first database and secured it using the wizard.
2) The first one cannot be open without the workgroup file (which is
what I'm looking for).
3) I make any other databases and they can still be open without
logging in. 4) The Wizard won't let me use a current workgroup file.
5) I can't change the change the Database owner from Admin (but I have
changed every other object in the database).

I assume number 5 is the problem, so how do I get around this and
secure the database. It says its encoded, but anyone can open the
thing without credentials.

*All* Access apps need a workgroup file, the default being 'system.mdw'. It
is good practice to leave this one alone and create new ones for
customisation.

If you can still open an Access file after applying user-level security
then you must have missed a step. This is essential reading:

<http://support.microsoft.com/default.aspx?scid=/support/access/content/sec
faq.asp>

There's also a step-by-step example on my web site.

Regards,
Keith.
www.keithwilby.com

 

[Jacques Latoison]

Thank you very much Keith.
You were a big help.
The part I was missing was having to make a new DB after attaching to my
workgroup file, then importing from the DB I was working in.