jwcolby
jwcolby at colbyconsulting.com
Thu Mar 13 11:00:02 CDT 2008
LOL. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Thursday, March 13, 2008 11:40 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Security permissions Yep, do this in several applications. I think it's tutorial time. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Wednesday, March 12, 2008 6:07 PM To: 'Access Developers discussion and problem solving' Subject: [AccessD] Security permissions - was RE: Feeding an paramarray to aparamarray LOL, thanks for the advice. ;-) That is the next iteration. Do you perhaps do this already? I am struggling with how to manage the various permutations in a functional user interface (wizard) for setting such permissions. Any given form has a "cancel" which prevents opening, as well as the four properties - AllowAdditions, AllowDeletions, AllowEdits and DataEntry. My LWS allows setting these properties but making them table driven makes the editing of the tables necessary before a form can have such security. My experience so far has been that the groups that can perform specific functions in forms are rather stable and so having them hard coded is not a big issue. The bigger issue is KNOWING what the permissions are. For that I am working on having the forms log their permissions as they open (through the LWS code). Thus while the permissions are hard coded, there is a set of tables which can display the permissions so you know where to go to make needed changes. Loading the permissions from tables is a goal though. Unfortunately (or fortunately) the LWS also allows setting permissions for controls on forms. Thus the problem gets radically bigger immediately. John W. Colby Colby Consulting www.ColbyConsulting.com The information contained in this transmission is intended only for the person or entity to which it is addressed and may contain II-VI Proprietary and/or II-VI Business Sensitive material. If you are not the intended recipient, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. You are notified that any review, retransmission, copying, disclosure, dissemination, or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com