Yes, it does!
Table 1 = “Events”; 1 record for each Event held with all the information specific to that event
Table 2 = “Employees”; 1 record for each Employee with all the information specific to that employee
Table 3 = a join table where Employees meet Events – “Attendance Records”; 1 record for each instance of an Employee attending an Event with all the information specific to that employee-attendance (such as the certificate)
While 40 may sound like a lot of views to make, it really isn’t that bad. Create your first view (which, if you use this 3 table route, will be in the “Attendance Records” table) with your filter for a person, and hiding any fields you don’t want visible; then use the 3 dot menu for a view to “Duplicate” that view – all you need to do is change the filter and the name.
If navigating all those views sounds like a nightmare, consider that you can simply type ctrl\⌘ + shift + K to open the search bar for views in a table and start typing a name – once the name you want is filtered down/selected, hit enter, and you will be taken to that view.
So if you have all these views named for the employee, you can then (if you need to) share an employees view with them, and as the title they will simply see their own name (the name of the view, not the name of the entire base). Here’s an example of a shared gallery view – the title of the entire base is “Assessment & Accreditation”, but all the external viewers of my shared view see is the title of the view I’m sharing:
