Database on networked drive

[Lisa]

Hi, everyone,

I have an MS Access 2003 database on a networked drive at the office.
When I created security for the database it put an icon on my desktop.
If I open the database via the icon, I get prompted for a username and
password and it works great. When I open the database by navigating to
the networked drive and double-clicking on the file, it opens and does
NOT prompt me for a password (it looks like it's picking the last
login name that I used when I logged in via the icon).

Since this is on a networked drive, I'd like users to be prompted for
a password if they open the database by navigating to the shared drive
and double-clicking on the file. I need role-based access, so I don't
see that setting one generic password is really an option.

Is there any way to force the database to ask for a username and
password no matter how it's opened??

Thanks,
Lisa

 

[Daniel Pineault]

When it comes to securing an access database properly your must always go to
the FAQ. I know it is a long read, but it is essential to properly securing
a db. You can find it at

http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp

 

[Albert D. Kallal]

It would be quite hysterically funny that if after securing a database, that
users can simply click on the database and not be prompted for password and
can use the database as they please.

If your databases secured correctly you'll have the following situation:


If the user takes the database home without the appropriate security
workgroup file, they will not be able to open the database.

If the user takes the database home without the appropriate security
workgroup file, but then create their all own security file they will NOT be
able to open the database.

If you lose the original security file, and have not saved the PID
information used when creating the security file you yourself will be locked
out of that file and will NOT be able to get into the file.

In other words it would be and laughable if security could simply be
circumvented by copying the filed or moving it to a different machine, or
simply choosing to use a different security workgroup file.


NONE OF THE ABOVE will get you into the database if you secured the database
correctly.

If you set up security correctly, when users click on the file they will get
an error message specifying to them that they do not have permissions to
open this file. If security has been correctly set up your users MUST use
the correct security file. You can specify the workgroup security file by
you using a shortcut, or simply having users joined that particular
workgroup file.

If the user has not joined or is part of that workgroup file when they click
on that database, they'll get a message to the fact that they do not have
permissions to use the database.

Once again, if you secure the database correctly then users MUST use the
correct security work group file, and furthermore if you lose that workgroup
security file then YOU will locked out of the file.

Simply making a copy, or creating your own workgroup file will not work if
you set up security correctly.