Solo712
Registered User.
- Local time
- Today, 03:44
- Joined
- Oct 19, 2012
- Messages
- 837
Hello everyone,
With the advent of the accdb format in A2007, setting up user security has become the developer responsibility. Luckily, to provide basic, “lightweight” security is not a difficult task. It consists of managing a database user table and providing the application with a login feature. The enclosed database provides an illusration of a User Security setup. My own applications use this format only with a few enhancements.
The frmUsers form manages the adding and editing of database user. Its functionality is not meant to be available to regular users but to a system administrator, who sets up initial passwords, and controls access levels for users of the database. In this demo, the access levels are simple 1-2-3, which would be in most applications converted to a more sophisticated access matrix matchibg users to individual forms, reports, attached documents, etc.
frmUsers utilizes several somewhat advanced features. It is a single record form which performs “controlled edits”. Under controlled editing a user is not allowed to leave a dirty form without either explicitly “saving” the added/edited record or “undoing” the changes. This prevents accidental changes to database records. (When form becomes dirty, an edit icon is displayed.). The form also performs encrypting and decrypting of passwords, and allows the admin to see them. With this setup admins are able to see password to prevent “borrowing” access. An added Windows username is there for a two-step identification.
frmSignOn is a login utility. It would be have to be succesfully negotiated for a user to enter the Database application. The form has an added function of allowing the user to change his/her password. This is accomplished by ticking off the check box under the password text box. The box must be checked before the Enter button is pressed with a valid password in the textbox. If a valid password was entered the display will switch to a “change password” screen and user will be prompted to enter a new password. If user cancels the operation he/she is allowed in under the old password. Note the multiuse password validation routine, the screen overlay design and the “remember the last user” feature of the ListIndex table. Finally, the Login utility provides a “secret” login bypass that allows the admin access without knowing the password. In the demo, the key combination is “Ctril-Shift Y”.
Hope you find this demo useful…
Best,
Jiri
With the advent of the accdb format in A2007, setting up user security has become the developer responsibility. Luckily, to provide basic, “lightweight” security is not a difficult task. It consists of managing a database user table and providing the application with a login feature. The enclosed database provides an illusration of a User Security setup. My own applications use this format only with a few enhancements.
The frmUsers form manages the adding and editing of database user. Its functionality is not meant to be available to regular users but to a system administrator, who sets up initial passwords, and controls access levels for users of the database. In this demo, the access levels are simple 1-2-3, which would be in most applications converted to a more sophisticated access matrix matchibg users to individual forms, reports, attached documents, etc.
frmUsers utilizes several somewhat advanced features. It is a single record form which performs “controlled edits”. Under controlled editing a user is not allowed to leave a dirty form without either explicitly “saving” the added/edited record or “undoing” the changes. This prevents accidental changes to database records. (When form becomes dirty, an edit icon is displayed.). The form also performs encrypting and decrypting of passwords, and allows the admin to see them. With this setup admins are able to see password to prevent “borrowing” access. An added Windows username is there for a two-step identification.
frmSignOn is a login utility. It would be have to be succesfully negotiated for a user to enter the Database application. The form has an added function of allowing the user to change his/her password. This is accomplished by ticking off the check box under the password text box. The box must be checked before the Enter button is pressed with a valid password in the textbox. If a valid password was entered the display will switch to a “change password” screen and user will be prompted to enter a new password. If user cancels the operation he/she is allowed in under the old password. Note the multiuse password validation routine, the screen overlay design and the “remember the last user” feature of the ListIndex table. Finally, the Login utility provides a “secret” login bypass that allows the admin access without knowing the password. In the demo, the key combination is “Ctril-Shift Y”.
Hope you find this demo useful…
Best,
Jiri
