FE/BE Access db and security issues 1

[sterlecki]

I am about to undertake my first Application DB that will be split and have security with it. Previous efforts have been stand alone apps.

1. Should security be added before or after splitting the app?

2. I plan to create copies of the front end to place on users local machines. Once security has been added to the FE will it also become part of the copies that I create from the secured version or will I have to add it to each copy?

3. I would like to protect the current queries, forms and code from the users but allow them to create their own tables, queries, forms, macros etc. Will the security measures for groups allow this?

4. Any other cautions or gotchas that I should be aware of before attempting this?

Thanks for your help.

 

[JerryKlmns]

1. I would secure it (remember to remove the default Admin user from the Administrators group and probably revoke all rights from the default Users group), then split it. That way new tables created in BE.mdb will inherit all rights for all groups(/users) enforced at first place.

2. A good strategy. Don t forget to share the new .mdw you ve created, over the network. You should also create a shortcut that opens your FE (which you could place it wherever you need on each PC) using the mdw file, or join the workgroup file at every PC. The first is to be created once and copied to all PCs plus using a different .mdw for different .mdb s, the second is to be done on each PC and enforcing all .mdb s to use the same, your, .mdw file.

3. These are permissions you enforce on new/existing objects for groups & users.

4. Safety First ---> Back Up Everything

Good Luck with this.

 

[sterlecki]

Thanks this clears some things up