Get a firm grasp on your IT environment when you learn Active Directory best practices with Veeam! Watch all, or choose any amount, of this three-part webinar series to improve your skills. From the basics to virtualization and backup, we got you covered.
Course Of The Month
2 days, 22 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
From security workgroup to login form in MS Access
Posted on 2013-01-03
hi,
I've got this little challenge this week.
I do have a MS Access built in 2003 using security workgroup. There is a function called "displayRights" with the following attribute
Public Function displayRights (userName As String) As Boolean
displayRights = GetUserBoolValue(userName,
End Function.
This is used to get the logged in username from that Workgroup and determine if he can access the price tags in other forms where VBA calls this variable.
What I would like to do is to create the same global variable (instead of changing the whole vba on each form.
I have create a login form, that calls a table where is myUser and myPassword. In the same table there is a field where I do specifiy (0 or -1) if the logged in user has right to access price tags.
The question is How can I store this login information so I can call it every time a form is opened and make sure the proper right is applied.
I've got this little challenge this week.
I do have a MS Access built in 2003 using security workgroup. There is a function called "displayRights" with the following attribute
Public Function displayRights (userName As String) As Boolean
displayRights = GetUserBoolValue(userName,
End Function.
This is used to get the logged in username from that Workgroup and determine if he can access the price tags in other forms where VBA calls this variable.
What I would like to do is to create the same global variable (instead of changing the whole vba on each form.
I have create a login form, that calls a table where is myUser and myPassword. In the same table there is a field where I do specifiy (0 or -1) if the logged in user has right to access price tags.
The question is How can I store this login information so I can call it every time a form is opened and make sure the proper right is applied.
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
3-
2
5 Comments
Active today
First: If you're using "a table where is myUser and myPassword." then you're not using User Level Security (or "workgroup" security). You're using home-grown security. There's nothing wrong with that, but it's best to be explicit when describing your situation to others.
I don't really understand what you're asking. You can call the "displayRights" function from anywhere in the project, assuming it's stored in a Standard Module. You'd use it something like this:
If displayRights("YourUserNam
'/ do something here
Else
MsgBox "You don't have permission to open this form"
End If
If you're asking how to "store login information" then, again, I don't really understand. If you have a User table, then you could simply include a boolean field named IsLoggedIn, and set that value to True whenever someone logs in. This can be troublesome at times - for example, if the program crashes, you'd have to reset that field to False for all users in order to start back fresh.
If all you want to do is just store the UserName of the person who logged in, then the simplest way to do that is with a hidden form. Add a textbox to that form named "txUser", and set the value of that textbox when the user successfully logs in. You can then refer to that textbox as needed:
If Forms("YourHiddenForm").tx
'/ do something here
End If
I don't really understand what you're asking. You can call the "displayRights" function from anywhere in the project, assuming it's stored in a Standard Module. You'd use it something like this:
If displayRights("YourUserNam
'/ do something here
Else
MsgBox "You don't have permission to open this form"
End If
If you're asking how to "store login information" then, again, I don't really understand. If you have a User table, then you could simply include a boolean field named IsLoggedIn, and set that value to True whenever someone logs in. This can be troublesome at times - for example, if the program crashes, you'd have to reset that field to False for all users in order to start back fresh.
If all you want to do is just store the UserName of the person who logged in, then the simplest way to do that is with a hidden form. Add a textbox to that form named "txUser", and set the value of that textbox when the user successfully logs in. You can then refer to that textbox as needed:
If Forms("YourHiddenForm").tx
'/ do something here
End If
THanks for your advise,
I will try to be more explicit.
In fact, I WAS using "User Level Security" ando NOT anymore since I have created a seperate table where I do store username and passwords as well as "displayRights" (field)
I just want to be able to display certain controls depending if "displayRights" is checked or not based on the logged in user.
I would like to explain it in a more simple english, but my french prevent me to do so ! :-)
My apologies ;)
I will try to be more explicit.
In fact, I WAS using "User Level Security" ando NOT anymore since I have created a seperate table where I do store username and passwords as well as "displayRights" (field)
I just want to be able to display certain controls depending if "displayRights" is checked or not based on the logged in user.
I would like to explain it in a more simple english, but my french prevent me to do so ! :-)
My apologies ;)
Active today
Okay - so you're logging in users with your own system, and you need to store the "logged in user"? If so, then the hidden form trick is the most reliable way to manage this.
Build a form named "frmHidden". On that form, add a textbox named "txUser". Set this form to start when the application starts, and make sure it's hidden. I assume you have a login form, so you'd open the hidden form when the user has successfully entered their password:
DoCmd.OpenForm "frmHidden", , , , , acHidden
Now write the user value to that form:
Forms("frmHidden").txUser = Me.YourUserNameField
Now you can refer to that form anywhere in your application like this:
Forms("frmHidden").txUser
So if you need to determine if the currently logged in user has display rights:
If displayRights(Forms("frmHi
'/ the user can see the prices
Else
'/ the user cannot see the prices
End If
Build a form named "frmHidden". On that form, add a textbox named "txUser". Set this form to start when the application starts, and make sure it's hidden. I assume you have a login form, so you'd open the hidden form when the user has successfully entered their password:
DoCmd.OpenForm "frmHidden", , , , , acHidden
Now write the user value to that form:
Forms("frmHidden").txUser = Me.YourUserNameField
Now you can refer to that form anywhere in your application like this:
Forms("frmHidden").txUser
So if you need to determine if the currently logged in user has display rights:
If displayRights(Forms("frmHi
'/ the user can see the prices
Else
'/ the user cannot see the prices
End If
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
| Title | # Comments | Views | Activity |
|---|---|---|---|
| SQL Job Failed | 6 | 31 | |
| SQL Server replace between tags | 6 | 30 | |
| Access 2010 Changing String to Date with Leading Zero | 11 | 32 | |
| ms/access follow hiperlink and generate image | 5 | 21 |
Preparing an email is something we should all take special care with – especially when the email is for somebody you may not know very well. The pressures of everyday working life stacked with a hectic office environment can make this a real challen…
You need to know the location of the Office templates folder, so that when you create new templates, they are saved to that location, and thus are available for selection when creating new documents. The steps to find the Templates folder path are …
With Microsoft Access, learn how to start a database in different ways and produce different start-up actions allowing you to use a single database to perform multiple tasks.
Specify a start-up form through options:
Specify an Autoexec macro:
Us…
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
Suggested Courses
Course of the Month2 days, 22 hours left to enroll
752 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.