I'm not saying this is the case here with the OP but I know someone who can't afford the O365 subscription for more user licenses, so they use the same login credentials for all users and just have a built-in login form to identify the actual user usingĪ table that stores a listing of all authorized users. Step 3: choose the Open tab and hit the Browse option. Step 1: Tap to the windows Start button and then hit the Access 2016 application. Hopefully in the near future they will include UserEmailAddress() in The following steps are applicable to Password protect Access 2010/2013/2016 Database. My question is this I have a main form on my application with command buttons to navigate through the different sections of my application. I cannot access the user information from a data macro which is extremely odd when you consider that the SQL Azure in the BE should know which user ID is requesting the changes/update/etc. Add Password Security to a Microsoft Access Command Button QUESTION I'm new to Microsoft Access and I'm currently working in version '97. To store additional information, you can create a table linking the login e-mail with additional information you need. Maybe that would work better than handling a completely independent user account table. I'm guessing you cannot use the built-in authentication of Sharepoint for your Access web app? In all honesty it's still very restrictive in that you cannot access the login name for table-level data macros, but all UI macros have access to the Use the built in system – it not only going to save you huge frustration, but it also works rather well. So I don’t recommend this idea and you really don’t have a lot of features and code that supports the idea of your own logon system. And as noted such a system is not much use since users must FIRST logon with You best you use the assigned user/logon and save yourself HUGE amounts of development costs and as noted attempting to build such a logon system in Access is not secure anyway. You attempt to build inside of your application will now not apply. All of a sudden they need to use some shared document folder and the password/logons And for the rest of the 365/SharePoint site they have to log into that system anyway.

You get none of these great built in security features if you attempt to roll your own. There are commands in the web system that allow you to get the user name and you can even use features to determine (and test/check) what security group a user is assigned to.Īll of that system is pre-built for you now. I much suggest you use the built in logon system for 365 (or SharePoint). I mean even in VBA (desktop), this was usually a poor idea and with the web you have even more limited programing abilities and thus this tends to be even worse of an idea. It makes VERY little sense to attempt to try and build your own security system.

This means they will have to logon two times. The main issue and problem is that users MUST first logon to the web site to be able to launch your form in the first place.

Ms access password field