Unable to access the link you posted.
@amicron - what you're showing is what I mentioned in my original post - controlling what a certain user can do (open forms, click buttoms, view textboxes, etc.). I have a free utility that does that using a custom system table so it uses record based "access rules" rather than VBA hardcoded rules.
https://forestbyte.com/ms-access-uti...access-levels/
What the OP wants is a totally different thing, the need here is to restrict data to a certain subset (so for example a manager can see only their department data). You mention that your third video is showing how to restrict the data for the current user's own records (probably by storing that in the table with a default from the login form), which is closer to what OP wants but still not quite. Restricting data can only be done by manipulating the form's (or report's) recordsource. With an Access back-end that can only be done by criteria in a query; for SQL Server, MySQL, Oracle and similar you can use views in the back-end to enforce the data based on the login permissions.
Cheers,
Works for me?
Please use # icon on toolbar when posting code snippets.
Cross Posting: https://www.excelguru.ca/content.php?184
Debugging Access: https://www.youtube.com/results?sear...bug+access+vba
Might be restricted through my organisation
Just tried link on my mobile, 403 forbidden. Will check security settings
Hi Guci@amicron - what you're showing is what I mentioned in my original post - controlling what a certain user can do (open forms, click buttoms, view textboxes, etc.). I have a free utility that does that using a custom system table so it uses record based "access rules" rather than VBA hardcoded rules.
https://forestbyte.com/ms-access-uti...access-levels/
What the OP wants is a totally different thing, the need here is to restrict data to a certain subset (so for example a manager can see only their department data). You mention that your third video is showing how to restrict the data for the current user's own records (probably by storing that in the table with a default from the login form), which is closer to what OP wants but still not quite. Restricting data can only be done by manipulating the form's (or report's) recordsource. With an Access back-end that can only be done by criteria in a query; for SQL Server, MySQL, Oracle and similar you can use views in the back-end to enforce the data based on the login permissions.
Cheers,
Any chance you could message me so I can access the link please.