By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,671 Members | 1,278 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,671 IT Pros & Developers. It's quick & easy.

Can user password be set before admin password?

P: 7
I am just beginning to implement user-level security in Access 2003. I created a user account and it is assigned to the users group. I would like to assign a password for this account (or for the users group), but am not given the option to do so. (I am trying under Tools > Security > User and Group Accounts > Change Logon Password.) Only the admin userid is available. Is it because there is currently no password assigned for admin that I can't set a password for the user I created?

The database is on a small secure network, but will be accessed through an automated process, and it is for this process that I want to assign a userID with fewer permissions. If I can do that without forcing everyone else on the network (all of whom use the default admin user) to enter a password going forward, it would be preferable.
Jul 26 '07 #1
Share this Question
Share on Google+
3 Replies

P: 7
I'm not sure if my question was inane, difficult, or just plain boring, but no one's picked it up. In the meantime I've discovered the answer which I will now post on the off-chance that someone will read it someday. As a side note, all the user/password functions mentioned below are found on the Tools >> Security menu in Access 2003.

In short, no. Setting the Admin password is the gateway to turning user-level security "on" (though it's not really off to begin with, just very permissive).

Creating a password for the Admin user causes the password prompt to kick in. Once the password prompt is activated, it is then possible to log in as another user (of course, you have to create the user first), and set the user password. Admin can clear passwords for all users (by default), but every user ID must set its own password.

However, engaging user-level security did not have the expected effect on remote queries, so I've cleared all passwords for now until I learn more. I am indebted to Jack MacDonald's excellent white paper, "How I Use Security with Microsoft Access," for confirming and explaining the results of my experimentation.
Aug 3 '07 #2

P: 1
On the contrary, thank you immensely. I got into a huge bind today and finding your post got me out of it, so I created this account just to say thanks. Thanks!!!!!
Aug 17 '07 #3

P: 7
Hey, this makes my day! Glad it was helpful.
Oct 23 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.