By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,871 Members | 2,575 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,871 IT Pros & Developers. It's quick & easy.

Design question: Permissions to view

P: n/a
When users are setup in my app, the administrator can restrict the products
that are available for viewing by the user. I have a table, Table 1, that
lists the User Name, Product ID and Viewing Allowed (True/False) for each
product.

But here's the problem. What happens when new products are added?
Administrators don't want to have to go in each time and activate those new
products for viewing.

How do I best handle this? I was thinking about having a checkbox on the user
setup form that says something like "Always allow all products to be viewed
by this user". Then the code could use this to automatically update each
user's viewing permissions.

If this is a good idea, how do I implement it? Create another table that has
User ID and All or Not All in it? If a user is allowed to view All Products,
then the code will show all products, even though Table 1 may not show the
user as having permissions to view each product (because there is currently
no code that updates Table 1 if new products are added to the system).

Advice, suggestions, etc is appreciated.

Thank you.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200605/1
May 13 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I think you would want to keep a separate table like you have it, which
allows for a many to many relationship between user and product. For easer
management, you could replace user name with group name. Then when adding a
new user, all you would do is add them to a group. When a new product is
added, have the system assign it to the current user's group and to any
administrator groups you want to create.

"rdemyan via AccessMonster.com" <u6836@uwe> wrote in message
news:602d608f60677@uwe...
When users are setup in my app, the administrator can restrict the products that are available for viewing by the user. I have a table, Table 1, that
lists the User Name, Product ID and Viewing Allowed (True/False) for each
product.

But here's the problem. What happens when new products are added?
Administrators don't want to have to go in each time and activate those new products for viewing.

How do I best handle this? I was thinking about having a checkbox on the user setup form that says something like "Always allow all products to be viewed by this user". Then the code could use this to automatically update each
user's viewing permissions.

If this is a good idea, how do I implement it? Create another table that has User ID and All or Not All in it? If a user is allowed to view All Products, then the code will show all products, even though Table 1 may not show the
user as having permissions to view each product (because there is currently no code that updates Table 1 if new products are added to the system).

Advice, suggestions, etc is appreciated.

Thank you.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200605/1

May 15 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.