DB Security

[Stitcho]

I know this question has been brought up a million times on here and I have done searches but everyone always refers to using the Workgroup Administration within Access to provide user level security. I have a database which uses this type of security but basically it is a complete pain in the backside. I run half a dozen databases off my computer and I have to change my workgroup file every time I open a new DB because I need to have different security settings on each DB.

Is there a way of securing a database without using the Workgroup option?

I found this but its not really any use because all it does is list the code for it and there are no step by step instructions for noobs like me - http://www.blueclaw-db.com/microsoft_access_security.htm

 

[KenHigg]

Another way that may help you is to reference the workgroup file you want to use in the command line of a shortcut to each database. Here's a sample:

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /wrkgrp "N:\MyCompany\Materiel Management\Parts Prov\Dept484\Database\Common\FrontDesk.mdw" "N:\MyCompany\Materiel Management\Parts Prov\Dept484\Database\FrontDesk\Frontdesk_XP.mdb"

 

[Stitcho]

Another way that may help you is to reference the workgroup file you want to use in the command line of a shortcut to each database. Here's a sample:

Thanks Ken I'll give that a try. It may become a little tricky though when I come to deploy it. This DB will be deployed onto a network that I dont know the structure of and have no access to (im developing it for a family member) and also I dont know what the installation paths and mapped network paths will be for each person as it will be accessed from people from different offices across a borough

 

[gemma-the-husky]

i don't think you will get acceptable performance trying to use access tables over a netwrok, other than with a LAN.

Try, but you will find that if a lot of data has to be moved, than the line speed will be a real limiting factor


with regard to linking tables, there are loads of solutions to do this dynamically. The point is that a connected/linked table (it will have an arrow in the database window) stores its path in the tabel definition, and this can be modified at run time, programmatically. Needs a bit of work, and an understanding of DAO or ADO. MS changed there default from DAO to ADO and then pack to ADO, so the solution may be affected by it which Access you have.