multi user security

  • Thread starter Thread starter John
  • Start date Start date
J

John

I have been asked to replace a single user database running on a
workstation with a multiuser alternative. Most of the workstations (4)
on site have Access 2003 installed, and a number of unrelated Access
databases exist for use by individual employees, with no security
restrictions imposed on them. My solution to the multi user bit is as
follows.

1. Create a data.mdb with all data tables to reside on a server share.

2. Create an Access front end (MDE) to deploy on multiple
workstations, containing forms using ADO for data manipulation.

I want to impose the following restrictions.

The front end has read write access to the data.

All users with MS Access can link (read only) to data.mdb for ad hoc
reporting, preferably without a password.

Only Admins can open data.mdb for full access with password.

All workstation users, including Admins, with MS Access can create and
access their own databases with no restrictions what so ever.

I have read about mdw files and my understanding is that they are used
on the client to restict access at user and group level to all
databases either on the client or on the server, if this is the case
its not suitable.

Can anybody point me in the right direction to impose security like
this on a single remote .mdb without limiting what users do on their
workstations, or, if my understang of mdw is wrong, point me towards
an explanation of mdw.

Thanks.
 
John said:
Can anybody point me in the right direction to impose security like
this on a single remote .mdb without limiting what users do on their
workstations, or, if my understang of mdw is wrong, point me towards
an explanation of mdw.

Thanks.
Click to expand...

Your plan with respect to splitting is a good one, as is your proposed user
grouping. However, to achieve your aim you'll need to apply user-level
security. This can be done without interfering with other "unsecured"
database if done correctly. I'd suggest having a look at my step-by-step
example to get a flavour of what you need to do and then dive into the MS
Security FAQ, the latter being essential reading. Links to both on my
website.

Work on copies of your files when you experiment and test your work
thoroughly.

HTH - Keith.
www.keithwilby.com
 
Have read your howto, I had missed the point about the shortcut,
thanks for your help.

John
 
Back
Top