User Control

[Mia_placidus]

I have put together an employee database that list
personnel, their duties, supervisors, addresses and phones.

This thing is currently living on a shared drive (with a
copy on my drive). I would like to make sure that:1)
Nobody inadvertently deletes the database, and 2) that the
unskilled users are ulikely to trash the thing with out of
place data or whathave you.

The main form in the database is presented by departments,
with subforms for the other data. This works fine and
seems to be pretty stable (the table relationships are
elementary).

What should be my approach here?
Can I set user passwords such that the various department
admins will have access only to those departments of
interest?

I tried setting up some data access pages, but they seem
kind of hinky to work with. If a DAP has subDAP's I seem
to lose the ability to edit in the subDAP's (save button
is greyed out. Uses a spreadsheet style DAP to present
phone numbers but the field widths in the form are jumping
all over to fit the data.

If I get the DAP's working, can I PW protect the database
and still allow data entry through the DAP's?

It looks like, if I password protect the database, then it
is totally locked up except for whoever has the password
in which case it is totally open. Help says you can set
various user level accesses, but doesn't say how.

Recommendations?

 

[Arvin Meyer]

If you allow editing, you allow a possibility for destruction. You reduce
that possiblity by adding security to the server, and user-level security to
the database. Adding validation on the forms and tables will reduce junk
data entry. The following FAQ will help with security:

http://support.microsoft.com/support/access/content/secfaq.asp

Make sure you read it thoroughly and implement it carefully.

You are correct about DAPs being a bit "hinky" I build regular asp pages
instead of using them. In your case, security will be easier to implement
than trying to use a web solution.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Guest]

Your reference to the FAQ was just what I needed. Actually
I think all of Access is kind of hinky, but I guess you
eventually get used to it. My major complaint is lack of
explanation for the syntax and really lousy examples.