How do I bind username password security to a specific database fi

[Guest]

I have multiple Access 2003 database files that are independent of each
other. After creating a workgroup information file and adding username
password security for one database file, that security was enforced for any
access database file that I opened on my pc. I wanted to have the security
tied only to one database file, which is to reside on a private network
folder. When opening the database file from other users' pcs off of the
network drive, no username was required to access the database until I joined
them to the workgroup file that was created, one by one. This security seems
pointless because anyone with access to the network folder can see the
database without typing a username and password (until they join the
workgroup). And on my pc, I have to type in the same password for any one of
my databases I am developing. Is there a way to setup the username password
security for one database file specifically?

 

[Rick B]

Then you did not secure the database properly. You need to read and follow
ALL the steps in the security FAQ on Microsoft's website. You did not take
your user out of the Admin group as instructed.

Step back and do it right. Do not skip any steps; they are all there for a
reason.

Rick B

 

[Guest]

Thank you Rick! I now have the database properly secured. I wasn't aware of
the security FAQ document. I am still wondering why my other access database
files all require the same username password security when they aren't
related to the database I secured. Any ideas? It seems that the security is
still tied to the entire app rather than the database file.

 

[Rick B]

Your databases don't stipulate which password is used, the security
workgroup (.mdw) file does. If you are joined to the workgroup which
contains your userid and passwords, then you will always be forced to sign
in. If you created a new workgroup file and used it for your secured
workgroup, then you could still use the default system.mdw workgroup file to
access all your other database files. Assuming the ADMIN user for the
system.mdw file does not have a password associated with it, you would be
able to open the other database files without a password.

The best way to do all of this is to join the default workgroup using the
workgroup administrator program that is part of Access. This will be the
workgroup used when you open a database. If you open your secured database,
you should get an error stating that that workgroup does not have rights to
your database. (This is how other users would be denied access to your data
if they try to open your database on their computers.)

To open your database, you would create (unless your security wizard did so
for you) a shortcut that includes the workgroup in the path. If you launch
your database from this shortcut, Access will use the defined workgroup to
gather the access information. Since this workgroup would have a password
tied to the Admin userid, it would require you to log in first.

The security FAQ should point all of this out.

Hope that helps,

Rick B


Rick B

 

[Guest]

Perfect! That's exactly what I wanted to know. Thanks so much!

 

[Guest]

I had the same problem recently and found that you can only use the shortcut
that the security wizard provides. If you use any other than you will have
problems. Don't join the new security file. Just use the short cut and
rejoin the original default security file.

 

[Joan Wild]

I had the same problem recently and found that you can only use the
shortcut that the security wizard provides. If you use any other
than you will have problems.

Could you elaborate? The wizard doesn't do anything that you couldn't do
manually.