low level security for a shared database

[Guest]

Access 2002
I am about to share a simple database with 3 other users. The DB is in a
shared folder on a network. I'd like to secure the DB so users can't get into
the design side and mess around. I just want them to enter data and Save. The
DB doesn't have any critical info; I'm just concerned about the "messing
around", although the users aren't familiar with Access.
I'm open to any suggestions. Thanks, Dan

 

[Rick Brandt]

Access 2002
I am about to share a simple database with 3 other users. The DB is
in a shared folder on a network. I'd like to secure the DB so users
can't get into the design side and mess around. I just want them to
enter data and Save. The DB doesn't have any critical info; I'm just
concerned about the "messing around", although the users aren't
familiar with Access.
I'm open to any suggestions. Thanks, Dan

Make a copy as an MDE and let them use that. An MDE automatically disallows
viewing or changing the design of any code-based objects (forms, reports,
modules). They could still see and edit queries and tables though. To
prevent that you would need to implement full-blown Access security which is
a more advanced topic.

It is relatively easy to "hide" these things from people who are not
familiar with Access. Check the options in Tools Startup.

 

[Immanuel Sibero]

Hi Dan,

For starters,
- Split your database to FE and BE. Put the FE on each user's local drive
and the BE on the network share (a must for multi users).
- Convert the FE to .mde.
- You can "lock" down futher by using your own menu structures, so that the
users can pick only the menu selections that you make available.

For more:
- Disallow bypass keys.
- Use Access User Level Security (ULS)


HTH,
Immanuel Sibero

 

[Guest]

Thanks, everyone. I'll go with the FE BE way. That's worked for me before.