Unsecure Backend After Splitting

[pat_nospam]

Help - Backend Unsecure after split

So I split my database and turned the front end into an MDE for final deployment (or at least version 1.0). After playing around with it today, I noticed that the front end is secured but the back end is not.

The front end can only be opened by its designated secured.mdw, as it was setup initially. But the backend can now be opened by secured.mdw, system.mdw or hackers.mdw!! How can I resecure the backend to secured.mdw and make my database safe again?

Thanks

Pat

 

[rockman]

I've had limited experience in securing my own databases, but I would perhaps state the obvious and recommend opening the mdb back-end and use the security wizard to now secure the back-end.

Warning: I do not know how this will influence your front-ends ability to access the data in the secured backend so DEFINITELY back-up the mdb prior to securing it.

Knowing all of the possible pitfalls of successfully securing a MS Access database, you have to double check each step of the process. This forum is replete with posts describing the headaches and solutions to accomplishing this.

I hope that this post will spur others more experienced in this area to address more specific problems you are encountering...

HTH,
Jeff

 

[pat_nospam]

Thanks Jeff for the advice - I had started wondering if I should just run the user level security wizard again for the backend, thus "resecuring" the database.

But I am worried about the front end then needed a second password or having issues connecting to the backend. I'll need someone to chime in to tell me that's not the case before I'm brave enough to try it I'll keep reading in the meantime and hope to find a solution.

Thanks again!

Pat

 

[RaeH]

Pat
I am by no means an expert and looked at various threads on various sites.
I am in the process of doing my first database and playing with the security issues.
As I don't really require lots of security a simple solution for the back end is to put a password on it.
Once you have done this then link your tables to the front end prior to converting it. That way you are only prompted for the password once. After you have converted the front end the user's can use it as normal (without needing the password). Data will still be saved to the tables but only the password will give access to the tables directly.

Hope this helps.

Rae

 

[l_jg]

Hi,

I can't get this to work! I've split my database, added an "on open" password to the back end, but when I come to relink the back end to the front end it errors saying "invalid password".

What am I doing wrong??

I'm using Access 97

Thanks
Lisa

Pat
I am by no means an expert and looked at various threads on various sites.
I am in the process of doing my first database and playing with the security issues.
As I don't really require lots of security a simple solution for the back end is to put a password on it.
Once you have done this then link your tables to the front end prior to converting it. That way you are only prompted for the password once. After you have converted the front end the user's can use it as normal (without needing the password). Data will still be saved to the tables but only the password will give access to the tables directly.

Hope this helps.

Rae

 

[ghudson]

You need to open up your back end with the same workgroup file that you are using for the front end. You should always use a custom shortcut to open your secured db's. Never join a PC to a workgroup. Here is what the Target: field of the shortcut should look like...

"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourFrontendDB.mdb" /user YourUserName

"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourBackendDB.mdb" /user YourUserName

Now correctly open the FE or BE and apply the permissions that you want to each object for each user.

Please ensure that you are making backup copies as you play with the permissions of you db since you just might lock yourself out as you learn how to do this!

Access security is tricky and I suggest that you do some searching of this forum so that you can learn from the other posters mistakes.

Good luck!

 

[RaeH]

Hi,

I can't get this to work! I've split my database, added an "on open" password to the back end, but when I come to relink the back end to the front end it errors saying "invalid password".

What am I doing wrong??

I'm using Access 97

Thanks
Lisa

Lisa

Not sure why you did an "on open". I just used the menu "Tools/Security/Set Database password"
That will secure the rear end only against anyone else interfering with it, unless they have your password.
Hope that helps.

 

[l_jg]

Thanks Ghudson and RaeH,

I've managed to sort it out - thanks for your help. My error was that Iwasn't deleting the links to the backend completely (i.e. using the split database wizard), and was then using the linking wizard to rejoin them, no password was asked for and the error message saying invalid password popped up. So, what I have now done is split the database manually, added the database password to the backend, relinked the tables from the file menu, which is where it asks for the password, thereafter it works well and doesn't ask for the password again.

Cheers!
Lisa

Lisa

Not sure why you did an "on open". I just used the menu "Tools/Security/Set Database password"
That will secure the rear end only against anyone else interfering with it, unless they have your password.
Hope that helps.