|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by 1William in Microsoft Access Database
Hey guys! Point me in the right direction here.
I have a slew of MS Access Apps (ver. 2000 and greater) that use a custom login screww. I have coding that identifies the users PC and NT login. Using that info, I lookup in a table to get the user name, and a few other key values. I also store a password in this table. The powers that be have requested I tie the login to the network login, as the users are forced to change it every 90 days. As I see it, I have two options.
1) At time of login, if the number of days passed since the last login is greater than 90, force a password change. Easy enough. I suspect they will want me to prevent reuse of a password for at least three resets. So this would require me to store the old passwords and check the new against them to ensure it is not a reuse. Again.not a big deal, just a few more fields in the user table and a little coding.
2) Use the same login as the network uses. This is by far the simplest method except... how do I verfiy the password the user just entered matches the network password? Is there a API call that can return a boolean?
Thoughts and opinions?
20091021-EE-VQP-81 / EE_QW_2_20070628
