Securing my Database.

[Guest]

I have an access Database and an Application that uses this database. The database is stored on a server and it is accessible to the client applications through a mapped network drive. I want to prevent users opening the database directly through network drive
Is it possible to set a password in Access where (Users need to be prompted for opening the Access Database and changing data, where as the Application does not require a password for reading and writing data into the tables)
Thanks in advance

 

[Chris]

Well, not really. The apps would have to have the same
password.

You could create a startup form, and on the Load event,
call DoCmd.Quit. The only way past that would be by using
the shift key bypass. If you disabled that (tools,
startup), the only way in would be to programatically
change that setting. If interested, I'll dig up that code.


Chris

-----Original Message-----
I have an access Database and an Application that uses

this database. The database is stored on a server and it
is accessible to the client applications through a mapped
network drive. I want to prevent users opening the
database directly through network drive.

Is it possible to set a password in Access where (Users

need to be prompted for opening the Access Database and
changing data, where as the Application does not require a
password for reading and writing data into the tables).

 

[Joan Wild]

I have an access Database and an Application that uses this database. The

database is stored on a server and it is accessible to the client
applications through a mapped network drive. I want to prevent users opening
the database directly through network drive.

You could start by hiding the network share (\\server\share$ rather than
\\server\share) where the mdb is.

Is it possible to set a password in Access where (Users need to be

prompted for opening the Access Database and changing data, where as the
Application does not require a password for reading and writing data into
the tables).
You could set a password on the backend mdb. For the frontend, you'd then
need to delete the table links and recreate them (you'll be prompted for the
password which would then be stored in the links). It wouldn't prompt the
users for the password in the frontend.

You could also set an autoexec macro in the backend, that throws up a
message telling them to use the frontend to make data changes. You
shouldn't even allow them to open the backend.

You'd have to disable the shiftkey bypass in the backend so they don't
bypass the autoexec macro.

Finally, you should be aware that the database password is easily found out.
There are cheap (even free) password crackers available on the internet.