Sharing a system.mdw

  • Thread starter Thread starter ccook
  • Start date Start date
C

ccook

Hi:
How is security distributed for a shared database if the system.mdw is
stored on each user's local workstation?
Thanks
 
First of all, you'd create a *new* workgroup file to secure the database
with. You would not use the standard system.mdw that ships with Access.

Once you've implemented security, you'd put the secure mdw on the server
along with the backend (you should split the mdb so that the backend
(tables/relationships) is on the server, and each user has a copy of the
frontend (all other objects, linked tables to the backend) on their
computer).

You'd then provide a desktop shortcut to users with a target like:
"path to msaccess.exe" "path to frontend" /wrkgrp "path to secure mdw"
 
Joan:

Thanks so much for your prompt reply. Is splitting the DB a must? I
wanted to keep this as simple as possible for this client. When you
set up a new database, what is the default workgroup? At the present,
the DB in it's entirety is on the server and everyone is opening it
using their local copy of Access. When one person sets up security on
their local workstation, they obviously don't see that anywhere else.
Is it easy to switch from the default to using a shared workgroup?

Carol
 
We have some users having MS access problem. They had a workgroup set up for
login MS access using a user ID and password for a particular file.Recently
they got office 2003 (it was office 2002 before). When I changed security on
Tools menu for MS access and join the workgroup using secure.mdw, it changed
all of MS access application, it asks password and user ID for all of MS
access documents. It didn't before. Do you know a way to correct this?


Many thanks!
 
Splitting is always recommended in a multiuser setting, or you risk
corruption.

The default workgroup when you first install Access is system.mdw It ships
with that and uses it in all sessions of Access (it silently logs you in as
'Admin').

Since system.mdw is the same on every computer, anyone can open an unsecured
mdb.

When you secure a mdb, you create a new workgroup file. If you follow the
steps properly, your database can only be used if the secure mdw is being
used.

The 'default' workgroup is the one specified in the workgroup administrator.

One person should not be setting up security on their computer alone.
They'd need to follow a series of steps to secure it properly. Then they'd
need to put the secure workgroup file on the server along with the backend.
Each user would then need a desktop shortcut to launch the secure database.

Security is a complicated topic. You need to study up and practice on a
copy of your database.
Security FAQ
http://support.microsoft.com/?id=207793

Security Whitepaper
http://support.microsoft.com/?id=148555

Although the whitepaper is old, it contains information to help you
understand security.

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm
 
ginger8990 said:
We have some users having MS access problem. They had a workgroup set
up for login MS access using a user ID and password for a particular
file.Recently they got office 2003 (it was office 2002 before). When
I changed security on Tools menu for MS access and join the workgroup
using secure.mdw, it changed all of MS access application, it asks
password and user ID for all of MS access documents. It didn't
before. Do you know a way to correct this?
Click to expand...

You are mistaken; if you changed the default to be your secure.mdw, then it
was used in all Access sessions. This hasn't changed.

Perhaps (before) your default was left as system.mdw and you had a desktop
shortcut to launch your secure mdb. The target would look like:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
 
thank you, Joan. I will try it.

Joan Wild said:
You are mistaken; if you changed the default to be your secure.mdw, then it
was used in all Access sessions. This hasn't changed.

Perhaps (before) your default was left as system.mdw and you had a desktop
shortcut to launch your secure mdb. The target would look like:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
Click to expand...
 
Back
Top