The variable glngCurrentUser is the Primary Key of tblUsers. This value is established when the Database Administrator sets up the User’s Account. The variable gstrCurrentUser is the actual name of the User (e.g. For example, the gstrUserID is the System User ID, returned from the Operating System. To explain my Public Variables, I like to allow the Database to have certain data always at its finger tips. The Global Constant will take care of that. Additionally, if I use these Global Constants throughout the Database, and need to make any changes to the actual values of these Constants, I don’t need to find every instance of the User Rights. I have established constants for the various types of Users because it is easier to remember the Type of User than it is to remember the value of their User Rights. Public Const UserSrRecorder As Integer = 5
Ms access switchboards how to#
Now that your Users Table is created, we need to figure out how to use it! This allows the Database to quickly add a signature block to outgoing E-Mails. Our office frequently sends out e-mail messages from the Database, so I have also included a User-customizable E-Mail signature block.
Ms access switchboards download#
Occasionally, our Users will download reports or spreadsheets from the Database, and having a User-established Directory helps to make sure their items are always in one place. Since our IT Department often requests a list of our Users’ machine names, I have included that in my list, and this, too, is easily obtainable from the OS environment.
The UserRights will be explained below, but this is a value indicating what level of access (or areas of access) the User will have. Only people who are verified users can access the Database. All our computers require Smart Card Access, so security is double-authentication throughout. The UserID is the value returned from the OS environment that identifies who is currently logged onto the machine. Allow User-specific access to the Database.Determine who has accessed the Database.Establish Public Constants and Variables.The method for doing this is rather simple: Over time, I have developed a method for limiting access to the Database, based on the User. Additionally, since nearly everything we touch is Privacy Act Information (I work for the Federal Government), we want to control access as much as possible. However, those 20 employees have vastly different roles in the Database. We only have 10 employees who use the Database on a regular basis, with sometimes 10 more who have a very limited access for short periods of time. I find myself in a situation like that in my work center. Then, every time one of these Objects is changed, all FEs containing that Object must also be updated. This can also cause a drastic duplication of effort, as some different Users (or different types of Users) may require the use of the same Objects. However, the obvious challenge with this solution is the constant expansion of different FEs. Another User requires a different set of Forms and Reports, so the Database Administrator builds another Front End that suits. When one User requires access to a particular set of Forms and Reports, those objects could be loaded into one Front End, linked to the Back End. However, when it comes to personal, confidential or even medical information, it behooves the Database Administrator to build into their Database certain safeguards to ensure that restricted information is not fallen upon casually or incidentally.Īnother solution would be to create separate front ends for each type of User. In most situations, this is not really a problem, because the average employee doesn’t want to sabotage their place of employment. However, the primary challenge with such an option is that you open yourself to a user “exploring” places of the Database they shouldn’t be exploring. One of the options for managing multiple users is to have a Switchboard or menu of activities that can be performed within the Database, and the Users will only select those items that apply to them, based on their responsibilities in the work center.
Ms access switchboards password#
However, we are still faced with the issue that once a User has access to the Database, they have access, since the password encryption unlocks the entire Database, not just certain parts. MS Access offers a bit of security with passwords that can encrypt the Database (both the Front and/or Back End) to limit who can open a Database. Many times, the Database will have multiple Users, and these various Users may (or may not) perform different functions within the Database. It’s usually built around the requirements of a Customer. Seldom does a Database Designer build a Database for themselves and themselves alone.