Good Afternoon All,
Okay--- I gave Admin a password in the database. But I still have users who can launch MS Access and the database comes up WITHOUT prompting them for a password.
I suspect that their default "system.mdw" file is coming into play.
When I take away "Admin" user's 'open/run' permissions in the database, they get an error dialog with an "OK" button and are not allowed to change their login userid to something other than "Admin".
Once somebody is in MS Access, they cannot change their login, correct ?
I've read all the articles I can get my hands on, and here's the problem I'm still having :
IDEA #1. "Create a shortcut" that specifies the workgroup file in the command line.
This is a nice idea, but what if the users can launch MS Access from their desktop and then they do so ? I want the users to be prompted for their userid/password REGARDLESS of how they start MS Access
IDEA #2. Have users run WRKGADMN.exe to "join" the workgroup file for the database so that it is in effect for them while they're using the database.
This is a nice idea, too...but again, if people can get into the database WITHOUT having to enter a userid/password, and MS Access automatically "assumes" that their userid is "Admin" if they're using the default 'system.mdw' file, what's the point ? The point here is that even though I have given userid "Admin" a password, and have stripped userid "Admin" of all of it's privileges, my users are still able to enter the database as userid "Admin"...even though they have no privileges as that user.
Also, if a user can only have 1 "current" .mdw file that they're joined to, what about those users that have more than 1 database that they use ? Do they have to run wrkgadmn.exe every time they want to switch databases ?
IDEA #3. "Push" the new .mdw file onto everyone's computer so that they have to use that one.
That's nice. A real maintenance nightmare. Everytime a password or permission changes, run the batch job at midnight and cross the fingers.
Have I missed anything ?!?
To summarize :
1. We have "x" number of users with MS Access installed on their machines.
2. Each user has his/her own "system.mdw" file that appears to be the only one that MS Access will accept unless a different ".mdw" file is specified in some sort of command line or shortcut command.
3. The "Admin" user in my database has no rights, and it does have a password.
4. Users on our network double-click the ".mdb" icon for my database, and enter it as "Admin", without having to enter a password, even though once they're in, they have no database privileges.
QUESTION : Is there ANY way whatsoever to specify that "this .mdb file" MUST USE "this .mdw file" ???
QUESTION #2 : At the very least, can somebody PLEASE tell me why the Admin password that I set up doesn't affect the users who have system.mdw files that specify that user Admin has a "blank" password ?
Oh wait...I just answered my own question....Microsoft stores userids and passwords in separate files outside of the database on EVERYBODY'S C: or D: drive !!!
WOO HOO !!! WHAT A CONCEPT !!!
MICROSOFT BABY !!!
WHERE DO YOU WANT TO GO TODAY ?!?!
Paul
Okay--- I gave Admin a password in the database. But I still have users who can launch MS Access and the database comes up WITHOUT prompting them for a password.
I suspect that their default "system.mdw" file is coming into play.
When I take away "Admin" user's 'open/run' permissions in the database, they get an error dialog with an "OK" button and are not allowed to change their login userid to something other than "Admin".
Once somebody is in MS Access, they cannot change their login, correct ?
I've read all the articles I can get my hands on, and here's the problem I'm still having :
IDEA #1. "Create a shortcut" that specifies the workgroup file in the command line.
This is a nice idea, but what if the users can launch MS Access from their desktop and then they do so ? I want the users to be prompted for their userid/password REGARDLESS of how they start MS Access
IDEA #2. Have users run WRKGADMN.exe to "join" the workgroup file for the database so that it is in effect for them while they're using the database.
This is a nice idea, too...but again, if people can get into the database WITHOUT having to enter a userid/password, and MS Access automatically "assumes" that their userid is "Admin" if they're using the default 'system.mdw' file, what's the point ? The point here is that even though I have given userid "Admin" a password, and have stripped userid "Admin" of all of it's privileges, my users are still able to enter the database as userid "Admin"...even though they have no privileges as that user.
Also, if a user can only have 1 "current" .mdw file that they're joined to, what about those users that have more than 1 database that they use ? Do they have to run wrkgadmn.exe every time they want to switch databases ?
IDEA #3. "Push" the new .mdw file onto everyone's computer so that they have to use that one.
That's nice. A real maintenance nightmare. Everytime a password or permission changes, run the batch job at midnight and cross the fingers.
Have I missed anything ?!?
To summarize :
1. We have "x" number of users with MS Access installed on their machines.
2. Each user has his/her own "system.mdw" file that appears to be the only one that MS Access will accept unless a different ".mdw" file is specified in some sort of command line or shortcut command.
3. The "Admin" user in my database has no rights, and it does have a password.
4. Users on our network double-click the ".mdb" icon for my database, and enter it as "Admin", without having to enter a password, even though once they're in, they have no database privileges.
QUESTION : Is there ANY way whatsoever to specify that "this .mdb file" MUST USE "this .mdw file" ???
QUESTION #2 : At the very least, can somebody PLEASE tell me why the Admin password that I set up doesn't affect the users who have system.mdw files that specify that user Admin has a "blank" password ?
Oh wait...I just answered my own question....Microsoft stores userids and passwords in separate files outside of the database on EVERYBODY'S C: or D: drive !!!
WOO HOO !!! WHAT A CONCEPT !!!
MICROSOFT BABY !!!
WHERE DO YOU WANT TO GO TODAY ?!?!
Paul