I have never tried to restrict what a person has access (Not Intended As A Joke) to. But my current class assignment requires that I present specialized switchboards to users based upon their credentials. The switchboards are not the problem - creating users, groups, etc. is. And then to deploy this system after they first log in, I expect, is another matter altogether.

For example, the den leader would need the ability to monitor everything in the database, including setting up the troop in the first place. He also creates users and groups, and is in charge of passwords. Then he creates users who perform various tasks within the troop.

For example, one of the cub scouts takes role at each meeting, and should only gain access to forms and reports pertaining to attendance.

Another boy takes care of recording whether they earned a particular badge, and then making sure someone orders it, and eventually pins it on who earned it.

This feels typical to the things most of you professionals do every day. And though mine is a labor of love, it still covers the same ground you have already covered. As a consequence, I would be overwhelmingly grateful if someone has already developed something along these lines would zip up the whole thing and send it to me.

I have never tried to restrict what a person has access (Not Intended As A Joke) to. But my current class assignment requires that I present specialized switchboards to users based upon their credentials. The switchboards are not the problem - creating users, groups, etc. is. And then to deploy this system after they first log in, I expect, is another matter altogether.

For example, the den leader would need the ability to monitor everything in the database, including setting up the troop in the first place. He also creates users and groups, and is in charge of passwords. Then he creates users who perform various tasks within the troop.

For example, one of the cub scouts takes role at each meeting, and should only gain access to forms and reports pertaining to attendance.

Another boy takes care of recording whether they earned a particular badge, and then making sure someone orders it, and eventually pins it on who earned it.

This feels typical to the things most of you professionals do every day. And though mine is a labor of love, it still covers the same ground you have already covered. As a consequence, I would be overwhelmingly grateful if someone has already developed something along these lines would zip up the whole thing and send it to me.

Thanks a 1,000,000 Chuck

Do your own homework! :) It's all on the Net and the Access help file
already.

Lookup MS's whitepaper on how to set up security then look at the
CurrentUser() function.
--
regards,

This is a very tall order for sure, but very do-able using User Level Security.
If you have never used ULS you must, not an option, read a lot of material
on the subject. It can be a difficult concept to grasp the first couple of
times. Practice on dummy databases until you really have a feel for it.

Having someone send you a working example will do you a disservice
on this subject. You must understand what is going on behind the scenes
with ULS, otherwise you will most likely screw things up. Not to mention
you will not have an answer when the instructor asks,
"Explain to me how you set this part up..."

Read all of the ULS information I have accumulated here on my site
(yes, read it ALL):

"Chuck Insight" wrote in message:
news:tg2ue.90644$xm3.8631@attbi_s21...

Hi All,

I have never tried to restrict what a person has access (Not Intended As A Joke) to. But my current
class assignment requires that I present specialized switchboards to users based upon their
credentials. The switchboards are not the problem - creating users, groups, etc. is. And then to
deploy this system after they first log in, I expect, is another matter altogether.

For example, the den leader would need the ability to monitor everything in the database, including
setting up the troop in the first place. He also creates users and groups, and is in charge of
passwords. Then he creates users who perform various tasks within the troop.

For example, one of the cub scouts takes role at each meeting, and should only gain access to forms
and reports pertaining to attendance.

Another boy takes care of recording whether they earned a particular badge, and then making sure
someone orders it, and eventually pins it on who earned it.

This feels typical to the things most of you professionals do every day. And though mine is a labor
of love, it still covers the same ground you have already covered. As a consequence, I would be
overwhelmingly grateful if someone has already developed something along these lines would zip up
the whole thing and send it to me.

This is a very tall order for sure, but very do-able using User Level Security. If you have never used ULS you must, not an option, read a lot of material on the subject. It can be a difficult concept to grasp the first couple of times. Practice on dummy databases until you really have a feel for it.

Having someone send you a working example will do you a disservice on this subject. You must understand what is going on behind the scenes with ULS, otherwise you will most likely screw things up. Not to mention you will not have an answer when the instructor asks, "Explain to me how you set this part up..."

Read all of the ULS information I have accumulated here on my site (yes, read it ALL):

Or you can make up a "pretend" security system where users login using a
simple form and user data is stored in a simple table.... not secure but
enough to fool basic users for non-critical data.
--
regards,

The zip file has instructions how to open the database.
Unfortunately, either the username or password have been modified since the
last time you saved it.
Please look into this and let me when it's safe to get it again.

"Br@dley" wrote in message: news:J6***************@news-server.bigpond.net.au...

Or you can make up a "pretend" security system where users login using a simple form and user data is stored in a simple table.... not secure but enough to fool basic users for non-critical data. Yep, very possible. A working sample here:

"Chuck Insight" wrote in message:
news:Niyue.81066$x96.14902@attbi_s72...

Jeff,

The zip file has instructions how to open the database. Unfortunately, either the username or password have been modified since the last time you saved it. Please look into this and let me when it's safe to get it again.