Secured database is not secure

[Angela]

I've created an Access 2000 database and used the wizard to create multiple
user/group security accounts and passwords. I removed the Admin user from
the Admins account, and made sure that the default User had no permissions.
When I use the shortcut (created automatically from the Wizard), I'm prompted
for a password etc. However, when I open the database from Explorer, I'm not
prompted for a password and have complete read/write/edit capabilities. What
did I do wrong? Why hasn't the Wizard secured the database? I understand
that when opening from Explorer, the database might be using the wrong
workgroup file to open the database but how do I prevent that from happening,
especially when others are opening the database from their workstations?

 

[Rick Brandt]

I've created an Access 2000 database and used the wizard to create multiple
user/group security accounts and passwords. I removed the Admin user from
the Admins account, and made sure that the default User had no permissions.
When I use the shortcut (created automatically from the Wizard), I'm prompted
for a password etc. However, when I open the database from Explorer, I'm not
prompted for a password and have complete read/write/edit capabilities. What
did I do wrong? Why hasn't the Wizard secured the database? I understand
that when opening from Explorer, the database might be using the wrong
workgroup file to open the database but how do I prevent that from happening,
especially when others are opening the database from their workstations?

When using the wrong workgroup the file should refuse to open. Check to make
sure that "Admin" is not the owner of any objects particularly the database
object.

 

[Joan Wild]

The wizard in 2000 is flawed; you should secure it manually.
Security FAQ
http://support.microsoft.com/?id=207793

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm

 

[Angela]

Thank you both, that was very helpful. I did indeed have an ownership issue.