Where to create the MDW workgroup

[Guest]

Hi,
I have seen ms wilds step by step and its awesome, but I have a few
questions.First I have a DB on a secure, shared drive, but no user groups or
permissions
set. It has now become apparent I need to restrict one field and probably
more later. I was wondering to I need to create the MDW on the shared drive?
and not locally on my machine? The DB is now used by 7 clinics throughout our
county and all of course by default are considered admin. I would like to
just restrict changing the one field for now, but believe the only right way
is to set the groups up. Is that correct?

 

[Scott McDaniel]

Hi,
I have seen ms wilds step by step and its awesome, but I have a few
questions.First I have a DB on a secure, shared drive, but no user groups or
permissions
set. It has now become apparent I need to restrict one field and probably
more later. I was wondering to I need to create the MDW on the shared drive?
and not locally on my machine? The DB is now used by 7 clinics throughout our
county and all of course by default are considered admin. I would like to
just restrict changing the one field for now, but believe the only right way
is to set the groups up. Is that correct?

You'd need to create the workgroup and place it somewhere that is accessible to ALL users ... this is normally on the
shared drive, of course.

Note also that ULS doesn't really do column-level security. You can use RWOP queries (see joan's site for info on those)
and restrict access to your tables, then provide queries to run forms/reports etc ... assuming you don't allow users to
directly access your tables, you can then determine permissions at the Form level (i.e. when the form Loads you can
Enable/Disable fields based on Group membership).

Have you split the database into Frontend (Forms/ Reports/Queries/Modules) and BackEnd (Tables only)? If not, doing so
would be advised (again, see Joan's site for help on this).

You mention "7 clinics throuhout our county" ... does each of those clinics have their own copy of the database? If so,
you'd need to secure all those copies, and make sure each clinic has their own .mdw drive ... if not, how are the remote
clinics accessing the database?

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Guest]

Hi Scott, Thanks, I understand now about the field. In other words when I set
the permissions for the user group I will lock the field I don't want changed
by anyone. Also, yes the other clinics have their own copy, in a sub folder.
And eventually they will need to be secured as well. If you have any other
suggestions or questions please reply.

 

[DAVID]

MDW is a database containing user names, group names,
and security ID's. Given a user name and Password, you
use it to look up ID's.

The rule for location is the same as any database:

On a network if you want to update the User name
or Password, and want other users to see your changes.

Local if the user names don't change, or if other
PC's don't need to use the user name and password.

So if you have a mdw that is used for admin or
development, other users don't need a copy of that.

(david)

 

[Guest]

Thank you David, I believe I understand your defining the Local vs the
network. I will post more info on how its going, but first I have other
problems to solve as it turns out. I originally created the db in acc. 97
then converted it fairly successfully to 00, but to no surprize to me the mde
creator wants to convert also. Something I hadn't anticipated. I may wind up
completely recreating the db in 00 in order to do what it is I need to do.