Access2000 Security in Network environment

  • Thread starter Thread starter JN
  • Start date Start date
J

JN

I'm trying to establish security for a database by using
selective permissions.

I have multiple PCs with different users sharing a
networked database.

I've figured out how to create the SYSTEM.MDW file on a PC
using the WRKGADM.EXE program. Once I've done this, I can
create users and groups, and can assign selective
permissions to forms, reports, etc... in the database.

Here's my problem:
- When I open the same database from another PC, it
doesn't have the same SYSTEM.MDW file, and doesn't
recognize/limit by user.

What do I need to do?
- Do I have to follow the same procedure on each PC that
will open the database?

- Can I put the "tuned up" SYSTEM.MDW file up on the
network somewhere and have all PCs point to it?

- Can I copy the file "SYSTEM.MDW" from my PC to each of
the other PCs?

- Other ideas?

Thanks

Jim
 
Place your secure .mdw file on the network somewhere and either have each
user's PC joined to that workgroup or, and this is preferred, create a
shortcut to launch your secure database and have that shortcut point to the
appropriate workgroup information file. The general syntax for the shortcut
is:

"FullPathToMSAccess.exe" "FullPathToDatabase.mdb" /wrkgrp
"FullPathToWorkgroup.mdw"
 
JN said:
I'm trying to establish security for a database by using
selective permissions.

I have multiple PCs with different users sharing a
networked database.

I've figured out how to create the SYSTEM.MDW file on a PC
using the WRKGADM.EXE program. Once I've done this, I can
create users and groups, and can assign selective
permissions to forms, reports, etc... in the database.

Bad idea to use the name "System.MDW" for a secure workgroup file. This is
the name used by the default workgroup on every instance of Office. You
want to be able to distinguish your file from those so use a different
name.

Here's my problem:
- When I open the same database from another PC, it
doesn't have the same SYSTEM.MDW file, and doesn't
recognize/limit by user.

*You* created a workgroup and joined it. Why would you expect that to
affect anyone else?

What do I need to do?
- Do I have to follow the same procedure on each PC that
will open the database?

That is one option, but not the preferred one.

- Can I put the "tuned up" SYSTEM.MDW file up on the
network somewhere and have all PCs point to it?

Bingo. Just change the name first.

- Can I copy the file "SYSTEM.MDW" from my PC to each of
the other PCs?

Again, another option, but not one I would recommend. In fact it is not
recommended that you even have people join your secure workgroup as that
affects every file they attempt to open. Just create a shortcut that
specifies your mdw file as a command line argument. Then it only affects
that application.
 
Back
Top