You sure can, and I actually do this quite often.
Setting up security and making it a user friendly type system for a
end user who will eventually have to manage the system is not hard.
However, it does take planning on your part.
You can teach the admin to how to use the security settings. however, to
make things easy, you as the designer probably want to setup things up
before hand.
For example, you can have the admin add a new user, and then start adding
what forms that user can use. That is going to be a LOT OF work if you have
100 forms. Also, if you allow the client to do that, then every time you
send a update, they will loose the security settings.
Hence, the best approach is to sit down and make up a bunch of
security groups. For my last project the groups I made where:
Basic user
Daily Reports
Seasonal Reports
Allow creation of Corporate Groups
Can forward date invoice payments
Can back date invoices payments
Can delete invoice payments
Add Tours, Rooms, Change Tour Pricing
Admins Administrator (Add users, change passwords)
As you can see, I sat down and made a bunch of security groups. So, for
example, in the above list I have something called seasonal Reports. Only
those users that need to view financial sales data for the year can thus use
those reports that have financial data. The same goes for only some users
can back date invoice payments. Of course most employees are not allowed to
back date invoice payment, and thus the daily sales slips, and the till MUST
be balanced at the end of the day. (if not, the employees must stay until it
is balanced).
The above idea of creating a bunch of security groups makes the whole thing
much easier. Now, all you have to do, is add a new users to the system (you
can use the security menu). You then simply add each group above to the
user. Most standard users get basic, and perhaps daily reports. In addition,
this means you NEVER actually have permissions for a user set in the actual
application. (that way, you can even send your client a new update
and the existing security settings will NOT be lost).
The real work in setting up the security is thus sitting down, and making a
bunch of sensible security groups. After that, the admin can quite easily
mange the whole system, even with the built in security system.
I actually did not like the security menu in ms-access, and thus I did write
my own. You can see some screen shots of this at:
http://www.attcanada.net/~kallal.msn/RidesSec/index.html
The above screens are so easy to use, that usually ZERO training is needed.
However, as mentioned the screens are not hard..it is sitting down and
making up some security groups is the hard part.
