Trigger Form Email Help

[Minty]

You don't need any of that information stored in the Manager info table - you can get that all from your employee table.
You simply need the EmpID , the Managers EmpID, and the Level 2 Managers EmpID. Just because they are a manager doesn't mean they end up with a different email or phone number does it?

And if that changes you have to update all those fields, twice, rather than simply changing the ID you have stored.



If the level 2 manager is always the managers' manager this is superfluous.

[rthom9]

The issue is how often the managers move around (so level 2 managers do change). I can see the value of having it all in one table, however. So I will have one table listing all employees (including managers), with the linked manager ID in a field for the employee. However, if my second table stores the employee ID and both level of manager's ID, wouldn't I need to update them both anyways?

So first table would have something like:

Emp ID Emp Name Emp Email Emp Job Title Emp Email Manager ID



And second table:

Emp ID Mgr ID Lvl2Mgr ID




Or, would I only store IDs in the second table, and remove from the first? (Don't know how I'd link them, if that's the case.)

I'm sorry. This is really my first foray into VBA and I just want to make sure I'm not messing it all up.

[Minty]

Yes you have the jist of it, you need to decide if you need the second table.
If you do then it's pointless storing the manager ID in the main employee record. Just use the second table.
If not then the MangerID in the main employee data is all you need.

E.g. if a employee can have two managers, or that the management chain is such that;
Burt and Fred report to John. John reports to Harry. However for Burt the second level manager is Tom, whereas Fred's 2nd level is Harry.
The above seems highly unlikely to me, but that is what the second table allows for.

The fact that the managers change frequently is immaterial, as long as the hierarchy is such that, the management chain is always employee¬manager¬managers manager, and there is no violation of that then you don't need the second table. You will still need to update your system in one place or the other.
With the single hierarchy it's much easier, only one record to update.