distribution and security

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

Guest

I see how you could have a short cut to use a particular mdw file on a
laptop. But if I want to distribute this database, how do I make it so the
same security is the same on all laptops? Do I have to distibute the mdw
somehow?
Thanks
 
sturner333 said:
I see how you could have a short cut to use a particular mdw file on a
laptop. But if I want to distribute this database, how do I make it
so the same security is the same on all laptops? Do I have to
distibute the mdw somehow?
Thanks

Yep. Unless you grant some permissions to the default Users group and only
want higher authorities for developers. In that case the user can use any
mdw file and they will be given the permissions you gave to the Users group.
Typically though a properly secured app can ONLY be opened when using the
proper MDW so you have to distribute that along with your MDB/MDE.
 
So my mdb is looking for a particular mdw? If so, where do I have the end
user save the 2 files?
Thanks
 
sturner333 said:
So my mdb is looking for a particular mdw? If so, where do I have the
end user save the 2 files?
Thanks

No. It is looking at the current user and his memberships (established when
the Access session starts) and then comparing that to what users and groups
have appropriate authorities in the MDB file. The MDB does not care what
MDW was used to obtain the user name and memberships. It only cares that
they match up with those that have permissions granted in the MDB. It just
so happens that there is normally exactly one MDW file that contains any
users or groups that the MDB recognizes.

Normally you would place the MDW in the same folder as the MDB and then
create a shortcut that opens the MDB while specifying the MDW to use. Such
a shortcut uses a target with the format...

"Full path to MSAccess.exe" /wrkgrp "Full path to MDW file" "Full path to
MDB file"

By using such a shortcut you can leave the user's *default* MDW file setting
alone.
 
Thanks for the help Rick. One more question, I hope. When I use the shortcut
method for using the mdw that I want ( "path to msaccess.exe" "path to mdb"
/wrkgrp "path to secure mdw" ), when I check Tools -> Security -> Work Group
Administrator, should I see the mdw I had in my shortcut or the standard mdw
that access uses?
Thanks
 
sturner333 said:
Thanks for the help Rick. One more question, I hope. When I use the
shortcut method for using the mdw that I want ( "path to
msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw" ), when I
check Tools -> Security -> Work Group Administrator, should I see the
mdw I had in my shortcut or the standard mdw that access uses?
Thanks

That will always show your default MDW, not necessarily the one that is in
use.

To see the one that is currently in use you can use the command...

SysCmd(acSysCmdGetWorkgroupFile)
 
I appreciate the help!

Rick Brandt said:
That will always show your default MDW, not necessarily the one that is in
use.

To see the one that is currently in use you can use the command...

SysCmd(acSysCmdGetWorkgroupFile)
 
I seem to be able to open the database either from the desktop shortcut with
one mdw and from inside of access with the default mdw. This changes the
permission of the user. How do I make it so the database requires the mdw
from the shortcut?
 
sturner333 said:
I seem to be able to open the database either from the desktop shortcut with
one mdw and from inside of access with the default mdw. This changes the
permission of the user. How do I make it so the database requires the mdw
from the shortcut?

The you missed a step in applying security. This means you fall into the same
category as 90% of users when attempting security for the first few times. :-)

When applied properly you should not be able to open the file at all unless you
use the correct MDW file. Check to make sure that the default user "Admin" is
not still listed as the owner of the database object. Owners haves rights even
if they don't explicitly have permissions. Otherwise I suggest Googling for the
detailed step by step instructions that are posted in this group frequently and
starting over.
 
Back
Top