Workgroup and Security Help

[Guest]

I am trying to secure a database that is on a network at work. By running the
wizard, I secured the database on my computer, but my co-workers down the
hall cannot enter the database. They get the message: you do not have
permissions...

First, how do I secure a database on a network? I believe the answer is
creating a workgroup on a common drive. But, if this is the case, can I
secure the database and then have other join the workgroup as I deem
necessary?

 

[Joan Wild]

I am trying to secure a database that is on a network at work. By running
the
wizard, I secured the database on my computer, but my co-workers down the
hall cannot enter the database. They get the message: you do not have
permissions...

Good, that means it's secured right. They are using the standard system.mdw
workgroup file that ships with Access. When you secured it, the wizard
removed all permissions for the Users Group and Admin User (common to all
mdw files), and so they can't use the database. The permissions are stored
in the mdb file.

First, how do I secure a database on a network? I believe the answer is
creating a workgroup on a common drive. But, if this is the case, can I
secure the database and then have other join the workgroup as I deem
necessary?

Yes. Put the secure mdw that the wizard created on your computer on the
network. As long as other users have installed Access to the same folder as
you, you can copy your desktop shortcut to them. Otherwise you'll need to
modify it for their computer. The target takes the form of
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"

You can use UNC pathnames rather than mapped drives in the paths.

Once you have this working, you'll need to split the database. From your
description you have a single mdb on the server that everyone is using.
That will likely lead to problems. It is best to split the mdb. Since it's
secure, don't use the splitter wizard. Split it manually - steps at
www.jmwild.com/SplitSecure.htm

Leave the backend on the server with the secure mdw. Give a copy of the
frontend to each user on their computer. Then you need to modify all the
shortcuts so that the "path to mdb" part is a path to the frontend on the
local computer, not on the network.

 

[Guest]

Great, thanks!
Also, my team and I began to discuss another option. Can I create a copy of
an unsecured database on the common, shared network folder, but maintain the
original database in my locked, secure personal folder. Then, I would run the
security funcion on the public database. In a sense, I just want to feel safe
with an unsecured backup file on my personal drive. Is this possible?

 

[Joan Wild]

It is always a good idea to implement a new feature/function on a copy of
your database. If anything doesn't work out, you've got a backup to return
to.

So yes, the first step is to create a backup of your unsecure mdb. I assume
your users need to continue to use the database until you have it secured.
In this case, you should split the database. Give each user a copy of the
frontend on their computers. Leave the backend on the server.

Now you can take a copy of the frontend and backend and put them on your
local computer. Proceed to implement security on your copy of the
frontend/backend. Once you have it working and fully tested, you can then
choose a suitable time (i.e. no one using the database), to apply the
security to the live backend, and distribute the secure frontend to each
user.