Help is here! It has come to WSI’s attention that some organizations feel “stuck” with Access 2003 because the user login controls function is available in that version of Access but not in later versions. You don’t need to be “stuck” in Access 2003 because of its built-in login controls. WSI can provide you with a simple and sophisticated alternative.
In order to enable login user controls in Microsoft Access 2007 and newer versions of Microsoft Access WSI offers its Access Login Database. It is designed for persons experienced with Microsoft Access database development to replace the Microsoft login controls that were present in Microsoft Access 2003 or to spare you from having to program your own user login control system using Microsoft Access’ built in programming language Visual Basic for Applications (VBA). If you are not an experienced Access database developer, WSI can help!
For organizations looking for a more sophisticated user control system, Microsoft Active Directory has recently been renamed Entra ID. If you are proficient in Microsoft Access database development, you can implement Microsoft Active Directory aka Entra ID yourself. If not, WSI can help!
Having WSI help has the benefit of single sign in and full integration with two-factor authentication and other related security. Once the database user signs into their device their assigned database use permissions can be automatically passed through to the Access database when they launch it. This will:
• Save time over entering yet another username and password
• Eliminates all the headaches for the IT department of managing another username and password
• Lock those users who leave the organization out of the data base, removing them from Active Directory / Entra ID
How can you tell if your database is using Access 2003 login controls?
Your database will include a file with the file extension .mdw.
Are there any “login permission free options”?
Yes, you can run an Access database without any logins if all the users need to have full access to everything the database can do or if it simply is not necessary to control what users see or do with the Access database. You can also create multiple Front End files (FE’s) one for each user type and just put the appropriate FE on the corresponding user’s computer. Each different FE has just the specific capability for its associated user type. All these different FE’s need to be linked to the same Back End files (BE) to ensure that everyone is seeing and working with the same data. If you aren’t familiar with what FE and BE are please read Microsoft Access Front End | Back End| Explained
WSI can help with user login control, other database problems, or if you want to create a new database. Reach out to WSI today!
https://www.microsoftaccessexpert.com/Microsoft-Access-2003.aspx
Continuity Planning for Independent Microsoft Access Database Developers
Are you an individual Microsoft Access database programming professional, who works on databases used by others? Don’t feel trapped, WSI can pick up right where you leave off and we will give those databases the care and attention they need to keep their owners’ organizations running smoothly.
