Overall Security Setup

[StacyStacy]

I have attempted to setup security for another database almost 6 to 12 months ago. When I attempted to setup security for a totally different database, I still see the old security settings for the previous db. What do I do? I there an easier way to setup security for each system that does not show up in a brand new db? If so, please help ...

Thanks!

 

[KenHigg]

Stacy, Sounds like you have either modified the default system.mdw or have set a new .mdw as the default using the workgroup administrator program.

The way I use multiple security .mdw's is to leave the default system.mdw in place and call the custom one from the command line when opening the database.

This is an example of what the command line in the shortcut would look like:

"c:\programfiles\office\access.exe" /wrkgrp "c:\documents\mydatabase\custom.mdw" "c:\documents\mydatabase\myDatabase.mdb"

Hope this helps...
ken

 

[StacyStacy]

Ok, Thanks. But how do I undo the default system.mdw? How do I call the custom one from the command line when opening the database.

 

[The_Doc_Man]

Right-click the Icon, get into the "Command line" that appears in the dialog box, and use ken's example.

For future reference: You should NEVER use the default SYSTEM.MDW file for a "live" workgroup file. Copy it to the directory/folder where your db resides. Rename it to match the DB's name (but keep the .MDW type). Join the new file in its new location. THEN start mucking about in it. While there are differing views on this, I see no reason to not name the .MDW file to match its associated .MDB file.

Technically, the names CAN be different because you manually join the workgroup or specify it in the command line (ken's suggestion). So you always have the option to supply a different name. There is no program advantage in having the names the same. I.e. nothing happens automagically if they match. But it just makes good programming sense.

 

[StacyStacy]

Thank you ... I was about to totally delete the .mdw file.

 

[StacyStacy]

I've made some headway and I have joined the security file to the db Thanks!

 

[ghudson]

I've made some headway and I have joined the security file to the db Thanks!

I do not advise doing that.

You should not join a users PC to a specific sercurity group. A user will have to log into any db with your workgroup info. That includes non secured dbs and even brand new dbs will require your workgroup info just to open the db. The users PC should be joined to the unaltered default System.mdw file.

You should use custom shortcuts to open the secured db with the correct workgoup file info.

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /wrkgrp "X:\YourWorkgroupFile.mdw" "X:\YourSecuredDBfile.mdb" /user UserName

 

[StacyStacy]

Ok ... now I am really clueless. Could somebody help me ... further. Can we set a phone call.

 

[StacyStacy]

How do I un-join the database to the security file? I have placed the command in my shortcut and it works. I want to be able to open other access db's without security.

Thanks!

 

[StacyStacy]

Ok! I did it! I un-joined the new db with the new workgroup that I created this afternoon by re-joining the workgroup administrator.exe to the default system.mdw file.

Now I can open up other access db's without a security prompt. And ... because I finally placed the command in the db's shortcut by calling up the Access program first, then the security file and lastly the database that I created.

If I'm wrong, please let me know.

Thanks.

 

[KenHigg]

Sounds like you got it to me!

kh