mdw security problem

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

Instead of creating a seperate mdw for my db I made the mistake of making
the security file apply to all db on my computer. Is there a way to undo
this security setting and instead create a sepearte mdw file for the specific
db.

Thanks,

Dan
 
You have probably joined your machine to the workgroup file you created. You
need to rejoin your machine to the default system.mdw file. To do that:

1) Do a filesearch for "system.mdw". If you find several use the one at
C:\Windows or C:\Program Files\Common Files\System
2) Run the Workgroup Administrator. If you're running Access 2002/2003, then
open Access (don't open a database), then click Tools - Security - Workgroup
Administrator. If you're running 97/2000 the do a filesearch for
"wrkgadm.exe" and run that
3) Click Join and locate the file you found in #1

You shouldn't be prompted for logins at this point.

Before proceeding with your security implemntation, I'd STRONGLY urge you to
read the MS Access Security FAQ:
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp
 
Daniel said:
Hello,

Instead of creating a seperate mdw for my db I made the mistake of making
the security file apply to all db on my computer. Is there a way to undo
this security setting and instead create a sepearte mdw file for the
specific
db.

The mdw applies to the session of Access, not to a specific mdb.

Did you create a new mdw, or modify the existing system.mdw.

If the former, then when it was created Access made it the default one to
use for all sessions. Just use the workgroup administrator to rejoin the
standard system.mdw. Then make a desktop shortcut for use with your secure
mdb. It's target would look like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

This will override the standard system.mdw for that session, but all other
instances of Access will use the system.mdw with no login.

If you modified the existing system.mdw, rather than creating a new one, you
didn't implement security properly. Follow the steps outlined in the
security FAQ exactly.
http://support.microsoft.com/?id=207793
 
Back
Top