|
|
 |
|
September 5, 2010
Register
|Login |
|
Frustrated with Microsoft Access?
Let the AccessUI supercharge your application.
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
|
|
 |
AccessUI Security Options
|
 |
|
 |
|
|
Click on image to expand
|
The Access User Level Security is without a doubt the most overlooked and most poorly understood feature of Microsoft Access. (So much so that Microsoft dropped it from Access 2007.) It can be extremely robust if correctly implemented, unfortunately if one of the 12 steps is not implemented properly, the security can easily be defeated – hence Access’ poor reputation when it come to security.
The AccessUI provides two different security models that control user’s ability to select tasks. The first model integrates with the Access Workgroup file and extends it capabilities. One of the major drawbacks with Access’ security is that it is reactive. A user clicks on a button to open a form and they are presented with a message that they don’t have permission to open that form. The AccessUI take a more proactive approach. If a user does not have permissions for a given task, that icon or menu item is not displayed. A developer stills need to apply permissions to each object they wish to protect, but the AccessUI can help create a very dynamic set of menus based on the user’s permissions levels.
The second AccessUI security model is new in version 2.6 and completely bypasses the Access User Level Security. Instead it uses the current user’s Windows login as their user ID. The advantages of this model are that the developer does not need to understand how Access Security works, and it eliminates having to maintain the workgroup file. The drawback of this simplified model is that it does not provide object level permissions and there is no support for groups, so each use must have their permissions set up independently.
By default, all users are able to invoke a task. To apply security to a menu item with either model, first a permission flag must be created. A permission flag is a token that can be associated with a user or group. These flags can then be associated with a Navigation Bar group or item, or a toolbar item. If an item has a permission flag associated with it, only users who are also associated with that flag will see the item. It will be invisible to all other users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|