jwcolby
jwcolby at colbyconsulting.com
Wed Mar 12 18:07:24 CDT 2008
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 -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Wednesday, March 12, 2008 5:14 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Feeding an paramarray to a paramarray Ok, a little off the original topic, but you shouldn't hard code permissions in code, because changing permissions then require code change. Instead, have the user's groups in a table, and the form's groups in a table, and have the two collections compare each other. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Wednesday, March 12, 2008 3:52 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Feeding an paramarray to a paramarray that is exactly what it is for and when it is needed it works well. For example I so stuff like allowing a form open for a set of Groups in my security. Thus in the form's OnOpen I call a function and pass in all the groups that are allowed to open the form. If the currently logged in user is in any of those groups the form stays open else the cancel is set and the OnOpen is exited. There is no way in advance to know what specific groups can open the form, it is hardcoded in the open event of each form. In cases like that it works quite well. John W. Colby Colby Consulting www.ColbyConsulting.com