Is this possible:

I have a database solution that I want to distribute. I want a master password that only I will know so as to lock out others from getting into the meat of the database. I will then have a second password that will give limited access such as define value lists, basic layout changes and the like.

But I cant figure out how to have this second password to allow the user to add other users and to set their access priv. while at the same time not allowing access to the master password or to its privledges.

LR

No. Only the "master" password can add other passwords (what you call "users").

You could of course set up, say, 20 different passwords (users) in your solution and just let the users change them.

Makes sense. How about another 2 questions.

I think I already know the answer to this one is no...but, if you are logged in as one user is there any way to set up a global field or script that can change the password of a particular other user?

And one last question...I know that if a user logs in there is a script that can be assigned to a button that can change the password, but is there any way that if this password is changed then the password that might be setup as a default login password will be automatically changed to match?

LR