Secured Workgroup Default Setting

[pat_nospam]

BE Security gone after split

Help! Every database I open, from unsecured databases to new databases, is now opening with the secured workgroup file that I set for a secure database. It means I have to type in my login information for every database?

How can I stop this from happening? I want to be able to create new, non secured (non workgroup) databases!

Thanks - Pat

 

[pat_nospam]

Okay - I found the reason it was having problems. However, in the process I also found that after splitting my database, the back end will accept any workgroup you assign to it!

The front end is properly secured and will only function with the workgroup it was assigned to, but the backend is wide open if someone changes the workgroup.

Can someone tell me how this happened?

 

[ghudson]

Your mistake was to "join" your computer to your secured workgroup. You should use shortcuts to open a secured db using your workgroup info [never join a computer to a workgroup]. Hopefully you did not alter your computers default workgroup file "System.mdw". All Access databases are actually secured using the System.mdw workgroup with Admin permission's. You need to rejoin your computer back to the default System.mdw workgroup file which is usually found in your Windows \System\ directory.

Below is a sample target field for a custom shortcut to open a secured db using a secured workgroup file...

"C:\Program Files\Microsoft Office\Office\msaccess.exe" /wrkgrp "X:\Testing\YourWorkgroupFile.mdw" "C:\Testing\YourDatabaseFile.mdb" /user TestUser

You should search this forum for the keywords "security" or "workgroup" or "system.mdw" (separately of course ;-) and you will find a lot of threads that will discuss how to implement Access security and you will also find a lot of threads where others have made similar mistakes and hopefully the solution is also posted within their threads. Access security is tricky to implement correctly so that the users are only able to access what you want within your application but it is a great tool once you have if figured out.

Good Luck!

 

[pat_nospam]

Right - I found the problem that I was joining into the system.mdw. My main concern now though is that after splitting my database, the backend will allow any workgroup to access it - even after joining the correct one, you can still switch to system.mdw and access it.

How do I lock this down? The front end works perfectly and will not allow an alternate .mdw to be assigned (only through desecuring with the Admin -> Users full access can you import/export, etc from other databases).

Thanks again - pat

 

[pat_nospam]

BTW - Thanks for the advice on the shortcuts. I've implemented them, and everything is working great now (I don't have to manually switch Workgroups through the Access Window).

I still am at a loss as to why my backend would lose it's security though.