General discussion

Locked

mdb and controlling the masses

By gcole ·
Our org. recently converted to MS office 97 suite and will begin training many users in Access db. My question is how would you propose the control of the mdb's, sharing, data security etc, Our environment is Novell 4.11 with NT4 workstations. Thanks for your input.

This conversation is currently closed to new comments.

11 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

mdb and controlling the masses

by VinnyD In reply to mdb and controlling the m ...

Since you have novell, I would use the Novell security to put the databases in folders accessable only to the users who need them.

It sounds like in your org. that any user can create their own database in access. That can be a nightmare trying to decide the security.

Collapse -

mdb and controlling the masses

by gcole In reply to mdb and controlling the m ...

The question was auto-closed by TechRepublic

Collapse -

mdb and controlling the masses

by j.monty In reply to mdb and controlling the m ...

Use the 'Make MDE file' option under Tools--utilities. That way, they can't modify tables and queries. Then use password security on the Files, and create views of just what you want them to see/have control over.

Collapse -

mdb and controlling the masses

by gcole In reply to mdb and controlling the m ...

The question was auto-closed by TechRepublic

Collapse -

mdb and controlling the masses

by frank.duffey In reply to mdb and controlling the m ...

Consider Converting to Win NT ver 4.0 Based Server This will allow you to Place all databases on a MS BackOffice Server.
Their is a security issue here which can be addressed with the WIN NT 4.0 Server running all DataBase Permissions and controlled by the Administrator only and not the end User.

Collapse -

mdb and controlling the masses

by gcole In reply to mdb and controlling the m ...

The question was auto-closed by TechRepublic

Collapse -

mdb and controlling the masses

by tysonmathews In reply to mdb and controlling the m ...

Create Group folders for say Finance, Documentation, Pantend dept. ETC.... and home Directories.
Then allow users access to there home dirs and there groups. But now people can have read rights to there groups home dirs but not write. That will prevent users from using others Home DIrs to save files and then if that user leaves ALL **** BREAKS LOOSE since you just closed that Home Dir. Force users to save to there dir.

Using NWADMIN32.exe will allow you to accomplish this task.

GOOD LUCK

Redmond, WA

Collapse -

mdb and controlling the masses

by gcole In reply to mdb and controlling the m ...

The question was auto-closed by TechRepublic

Collapse -

mdb and controlling the masses

by Bob Sellman In reply to mdb and controlling the m ...

There are a number of different situations than can occur.

Security is best controlled through the network software. Each user or group of users (depending upon what they are doing) should be given rights (read/write/etc) to one or more directories appropriate to their work.

If users are creating applications for their own use only, I would strongly recommend that they keep the application mdb files on their own workstations, since Access creates a lot of network traffic that would be unnecessary for single user applications. (Just copy to a directory on the network server periodically for backup if you want.)

For multiple user applications you should try the following:

1. The database should have a back end mdb file which only contains the tables (and relationships) and nothing else. Put this in a directory to which all users of the data have read/write access. (Yes, this is a weakness, but even internal Access security does not prevent people from linking to a database.)

2. The front end (application) should be in separate directories to which only the appropriate people/groups have rights. This way you can have, for example, a manager application and a data entry application (subset of the manager application) and the data entry person can only see the data entry app, while the manager can see and use both.

3. Creating MDE (rather than MDB) files for the application databases also helps, since the MDE files don't include any VBA code.

4. Be sure to remove as many Access menus, etc., from the applications to be used by multiple users so they aren't "tempted" to play around.

I would also suggest that your network security should use groups, rather than specific users, so that if users change (as they will), it's easier to manage security.

Good luck.

Collapse -

mdb and controlling the masses

by gcole In reply to mdb and controlling the m ...

The question was auto-closed by TechRepublic

Back to Community Forum
11 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums