🔔 For next video timeline see News Board at skillheader.com/ 📚 Download Files by Subscription skillheader.com/master-business-accounting-project-subscription/ 🌍 Complete Overview of the Project skillheader.com/building-master-business-financial-accounting-in-ms-access/ 📣 Join and Visit our Forum for Questions and Discussions skillheader.com/community/master-business-accounting-project-forum/ ☕ Support Us with a Cup of Coffee skillheader.com/support-us/
this is the video i was searching every time in youtube. real appreciate for your tired to learn within this video. don't think about or convenience about viwes in this video series, continue it. i will waiting for every videos to complite this big project
Wonderful video, thank you for the great skills, I am stuck with the AddUser Submit button update on the main dashboard issue. I think it has to do with the usermanagementsub form naming can anyone help?
Nice work Some how you use backward design tech. from forms to tables but you using it well👏 also using your unique vba formating is differant than usual 😮 but have a lot of tricky points Well done and waiting for next video
Stunning abilities with the code, i followed step by step all steps, i even got the same errors as you lol If you could slow the video a bit that would be perfect 🤘 Otherwise, keep up the good work 💪
Working out really well, like your approach as it simplifies some very difficult areas. one question though! How are duplicate usernames handled in the login process...seems like we can have multiple users with same login names as it stands now? is that something that is coming down the pike? I tried indexing the uUsername in the User table, but that started crashing the vba code for the submit button "refresh" function.
Great videos!! I happened to notice that you might have left out a section when creating the Edit User form. You don't show yourself making any of the changes to the coding section where fields are changed from AccountName to uName, etc. And also above that, there's no showing that you removed all of the password coding and also changed the close button form to the "EditUser" form.
Hi, thanks for your comment and support. Let me explain in a simple way to understand: All unbound text boxes are used with the addition of "txt" with each. The reason is that: the bound with table fields text boxes update whenever you enter data into them and an Undo function has to be used if you want to cancel the data or close the form without submission but the unbound text boxes update the record into the tables at once while clicking on the Submit button. On the other hand, you can watch the Edit Form section again, I have deleted the rest of the text boxes because the user can change the password while login. Now, hence the bound text boxes have to be used for edit data and the record will be updated upon changes to each text box, there is no need to involve the process of updating the table fields like the "Add New User" submit button. One thing to point out here that you are right that the associated codes with the removed text boxes should be deleted from the coding. Hope it helps.
@@skillheader Great information. The part that I'm specifically talking about is the line that says DoCmd.Close acForm, "EditUser" - You don't show changing it from "AddUser" to "EditUser" , unless I missed that part? Then when you're deleting the larger section of code from the submit button, the part at the beginning of the code where it says - If IsNull(me.txtAccountName) = True was changed to If IsNull(me.uName) = True ... did this part happen automatically when you bound the field or did you have to manually change those names in the coding part because that's where I'm not seeing the change in the video. Sorry for asking so many questions!! I appreciate your help!
I created event Log when the there is unsuccessful log in like when username and password are empty. in this case the uID is unknown or is null. i created an user i named "unauthorized " and profile "NoProfil" to deal with this situation. do you think it is good practice to do so.
In the Login Button code, just move the "aprofile" line before "Docmd.OpenForm...". Hope it will work and thanks for highlighting. I will try to update this in the next part of the series.
When using VBA code used to mask and unmask the password on a continuous form it applied on all records in the form is there a solution to apply on current record
There is a complex solution if you want it from the continuous form. Hence, continuous form always contains limited fields of information, you need to open another dialog mode form. You will get benefits of all the user data available and other is to use the mask or unmask from a pop up form.
🔔 For next video timeline see News Board at skillheader.com/
📚 Download Files by Subscription
skillheader.com/master-business-accounting-project-subscription/
🌍 Complete Overview of the Project
skillheader.com/building-master-business-financial-accounting-in-ms-access/
📣 Join and Visit our Forum for Questions and Discussions
skillheader.com/community/master-business-accounting-project-forum/
☕ Support Us with a Cup of Coffee
skillheader.com/support-us/
This is an application developed by real professionals. Congratulations! Your remarkable work shortens the learning process for beginners (like me :)
Thanks for your valuable feedback. We are happy to hear that our hard work is providing a unique learning experience on UA-cam.
Great and inspiring work can't work to learn to the finish of al the series God Bless you Sir.
Thank you very much and I wish you always success. Sorry if I am wrong because I am Kurdish ❤❤❤ 🙋♂️🙋♂️
Great job 🎉❤❤❤
Great again. Thank you!
Thank you are your love and support. It means a lot to us.
thanks for this material it helped me a lot please Contentious more
this is the video i was searching every time in youtube. real appreciate for your tired to learn within this video. don't think about or convenience about viwes in this video series, continue it. i will waiting for every videos to complite this big project
Your words mean a lot to me. Thanks for the appreciation and encouragement. Stay tuned, there is lot more than you expect.
Valuable videos. Do you want to continuous all the project ?
Great videos
Awsome...!!! Yur way of elaboration is fantastic. Thanks for sharing such as helpful material
This is awsome thanks. Loving the nice work.
Awesome , GO ON
thanks sir
Great work done!
Please when will the next part be ready?
It is great to have your comment. Please hit the bell icon if you have subscribed to the channel so the next video notification can be received.
Thank you
Wonderful video, thank you for the great skills, I am stuck with the AddUser Submit button update on the main dashboard issue.
I think it has to do with the usermanagementsub form naming
can anyone help?
solved it 😅
Nice work
Some how you use backward design tech. from forms to tables but you using it well👏 also using your unique vba formating is differant than usual 😮 but have a lot of tricky points
Well done and waiting for next video
Stunning abilities with the code, i followed step by step all steps, i even got the same errors as you lol
If you could slow the video a bit that would be perfect 🤘
Otherwise, keep up the good work 💪
Thanks for your love and support. Your suggestion will be considered in future videos. Stay tuned.
You have the option in your own YT settings to control the playback speed. You can slow it down yourself. Hope this helps!
Working out really well, like your approach as it simplifies some very difficult areas. one question though! How are duplicate usernames handled in the login process...seems like we can have multiple users with same login names as it stands now? is that something that is coming down the pike? I tried indexing the uUsername in the User table, but that started crashing the vba code for the submit button "refresh" function.
Ok, please watch this video for a better approach to handle duplicate usernames:
ua-cam.com/video/QVufaz1j2Lc/v-deo.html
Great videos!! I happened to notice that you might have left out a section when creating the Edit User form. You don't show yourself making any of the changes to the coding section where fields are changed from AccountName to uName, etc. And also above that, there's no showing that you removed all of the password coding and also changed the close button form to the "EditUser" form.
Hi, thanks for your comment and support. Let me explain in a simple way to understand:
All unbound text boxes are used with the addition of "txt" with each. The reason is that: the bound with table fields text boxes update whenever you enter data into them and an Undo function has to be used if you want to cancel the data or close the form without submission but the unbound text boxes update the record into the tables at once while clicking on the Submit button.
On the other hand, you can watch the Edit Form section again, I have deleted the rest of the text boxes because the user can change the password while login. Now, hence the bound text boxes have to be used for edit data and the record will be updated upon changes to each text box, there is no need to involve the process of updating the table fields like the "Add New User" submit button.
One thing to point out here that you are right that the associated codes with the removed text boxes should be deleted from the coding.
Hope it helps.
@@skillheader Great information. The part that I'm specifically talking about is the line that says DoCmd.Close acForm, "EditUser" - You don't show changing it from "AddUser" to "EditUser" , unless I missed that part? Then when you're deleting the larger section of code from the submit button, the part at the beginning of the code where it says - If IsNull(me.txtAccountName) = True was changed to If IsNull(me.uName) = True ... did this part happen automatically when you bound the field or did you have to manually change those names in the coding part because that's where I'm not seeing the change in the video. Sorry for asking so many questions!! I appreciate your help!
I created event Log when the there is unsuccessful log in like when username and password are empty. in this case the uID is unknown or is null. i created an user i named "unauthorized " and profile "NoProfil" to deal with this situation. do you think it is good practice to do so.
In the Login Button code, just move the "aprofile" line before "Docmd.OpenForm...". Hope it will work and thanks for highlighting. I will try to update this in the next part of the series.
Impressive tutorial. What font type are you using in your IDE for coding
Thanks for your support. I am using the font name "JetBrains Mono SemiBold"
When using VBA code used to mask and unmask the password on a continuous form it applied on all records in the form is there a solution to apply on current record
There is a complex solution if you want it from the continuous form. Hence, continuous form always contains limited fields of information, you need to open another dialog mode form. You will get benefits of all the user data available and other is to use the mask or unmask from a pop up form.
Do you run a discord channel? I think it would be SUPER helpful :)
How to download?
Thanks for your like and support. This project is on the go and will be available for download once completed. Stay tunes.