Linked database password

[Guest]

I have a typical split database and am trying to create a non workgroup
secuity environment. In order to protect the tables, I thought I could
create a database password, and somehow provide that password through VBA
when I opened the front end application so that the links worked. Has anyone
done this, or are there any other suggestions as to how to protect the back
end database?

 

[Joan Wild]

The database password is very weak, but you can use it if you like. Once
you set the password on the backend, open the frontend and delete the links.
Then recreate them using File, Get External Data, Link Tables...It will
prompt you for the password. It only needs to be done once as the password
is then saved with the link.

To lock/hide the backend further (you're really just putting up roadblocks)
- put it in a hidden share on the server \\servername\share$ rather than
\\servername\share
- create an autoexec macro in the backend that throws up a message, and then
quits (you can hold down the shiftkey to bypass)
- you can also disable the shiftkey bypass in the backend if you think users
know about this; but they'd also have to know the password

 

[Guest]

Thanks Joan. I am really only keeping the honest people out but it is better
than nothing.

 

[kingston via AccessMonster.com]

If possible, use VBA to create links on the fly via the command:
DoCmd.TransferDatabase acLink...

Make sure to delete the link quickly and appropriately (trap errors):
DoCmd.DeleteObject acTable...

Make your front end a .mde file to hide the code. Yes, you are only keeping
the honest people out, but I think that this makes it much harder.

I welcome and would appreciate other people's ideas and suggestions
concerning a solution to the OP's question.