Adding password to split database with multiple users

Question

Hello,

I created an Access 2010 database and have split it. I know I will need to re-link the tables after adding a password to the front and back ends. This database will have multiple users.

My question is: Will adding a password disrupt them from being able to add records simultaneously from their respective front ends? I ask because when you go to add a password it mentions record level locking will not be enabled.

Thanks in advance for any info and help!

Answer 1

I wanted to put out one more bit about securing your DB but first why was SQL not an option? The express version is free and holds so much more data then Access. There are more then I am will to type right now but here are some of the high lights to help you out. 

Note: some of these are VBA coding. I can help with that. 

Remember, this is for the copy you are going to deploy! A lot of these will make it so you will not be able to get back into it. Always have backups. 

1. Hide database window shut down special keys The settings are here:

Of course the database is a big deal and some special keys allow you to bypass these options on start up (getting to that). Things like F11 that brings up the solutions list and holding shift down while opening the database to release it. 

2. Next you shut down that shift key! I know you don't work with VBA a lot yet but that is the only way I know to do it. It uses the "AllowBypassKey property...ie -Shift. There is a method to use a Macro though. That is a big piece. if you want the code i will send it. 
3. Take away the objects. Navigational Plain, Menus, etc. You can do that in options. Makes it much harder to get to things. 

Last but not least...the actual database where the information is held. That of course is a dangerous one. even more so because in a lot of chases it is a file that can even be deleted, not uninstalled. Be very careful with this one and for sure do not keep them in the same place.

As far as the login problem with the code. Feel free to post it so i can take a look if you would like.

Answer 2

I've actually saved about five separate copies trying to be safe. Then I update my copies if I've made any changes that day that I want to keep. A couple I use just for testing stuff on.

In regards to VBA, complete beginner. I tried to use it with a previous login/password form that had some code with it that I found by google searches, but just couldn't get it to function properly consistently. So that's why I opted for the legacy encryption in the interim until I could hopefully get it figured out eventually. 

So as far as security, I just have the legacy password and the navigation pane hidden.

Answer 3

That's perfect. But, just for clarification and trying to flatten any bumps before production starts, do I split and have them access the front-end on the shared drive? Or OK as not split on shared drive? I noticed you said 'one copy on the shared drive' and then 'leave the front end in one spot.' I just want to make sure I understand you correctly. 

Again, your patience is very much appreciated. I apologize for the head ache in explaining.

I updated that. You really want to split on while still on your hard drive. I have down both but it can cause issues doing it on the server. The way it works is they are "tethered" ish through their connection. You will be able to move them and they will still be able to talk to each other. So don't think that you are locked into that if you decide to move it.

Answer 4

That's perfect. But, just for clarification and trying to flatten any bumps before production starts, do I split and have them access the front-end on the shared drive? Or OK as not split on shared drive? I noticed you said 'one copy on the shared drive' and then 'leave the front end in one spot.' I just want to make sure I understand you correctly. 

Again, your patience is very much appreciated. I apologize for the head ache in explaining.