J
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
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