security.mdw

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

Guest

I have copied an app from one machine to another. On the source, the app was
on the desktop and so was security.mdw.

Where (folder) do I need to copy security.mdw in order to regain access to
the app on the new machine?

Environ:
Acc 2003
WinXP

Thanks
LDN
 
roccogrand said:
I have copied an app from one machine to another. On the source, the
app was on the desktop and so was security.mdw.

Where (folder) do I need to copy security.mdw in order to regain
access to the app on the new machine?

Environ:
Acc 2003
WinXP

Thanks
LDN
Click to expand...

Access itself chooses the MDW file not the MDB you are opening. If one is
not specified as a command line argument then the default workgroup for the
current Windows User is used. On a default install of Office that would be
the System.mdw file stored at whatever the default location is (varies from
one Office version to the next).

You can use the Workgroup Administrator Utility to see what the current
default workgroup file and location is and also to change the default to a
different one. However; the standard advice is to leave the user's default
workgroup alone and create a shortcut that specifies the desired workgroup
as a command line argument. The syntax of that is...

"path to MSAccess.exe" /wrkgrp "path to MDW" "path to MDB"
 
Thanks Rick.

I copied security.mdw to my desktop, which probably wasn't necessary.

I then, using Sco's advice, used the Work Group Administrator to Join my
database to security.mdw.

LDN
 
roccogrand said:
Thanks Rick.

I copied security.mdw to my desktop, which probably wasn't necessary.

I then, using Sco's advice, used the Work Group Administrator to Join my
database to security.mdw.
Click to expand...

But again, you didn't actually "join your database to the security.mdw". What
you did was make security.mdw the default workgroup for that user logon of the
PC. Now EVERY MDB file that they open will require that they log on because of
this. That is why it is not recommended to use the Workgroup Administrator to
change the user's default workgroup.
 
Understood. But I am the only person using any of my applications, on any of
the several machines that I use.

I will keep this in mind in case I ever develop an app for multiple users.
I am finding that the security process does take a bit of getting used to and
my advice to anyone reading this thread is to practice it over and over on a
nonproduction database first.

LDN
 
Back
Top