Forum Discussion
QuickBaseCoachD
7 years agoQrew Captain
A table can be relation to itself. So 1 Manager May have many employees. Except that the managers are actually Employees.
So then the actual relationship is that 1 Employee have many Employees. The field that the system will create called [Related Employee] should be renamed to [Manager] and then it should make sense.
As for Jane seeing Bill, who is two levels down from her, I think that is possible to do.
But having said that, I�m not sure it�s intuative for users when set up that way. There is an arguement for setting it up more traditionally, where each employee has 3 slots called Manager Level 1, Manager Level 2, Manager Level 3.
So then the actual relationship is that 1 Employee have many Employees. The field that the system will create called [Related Employee] should be renamed to [Manager] and then it should make sense.
As for Jane seeing Bill, who is two levels down from her, I think that is possible to do.
But having said that, I�m not sure it�s intuative for users when set up that way. There is an arguement for setting it up more traditionally, where each employee has 3 slots called Manager Level 1, Manager Level 2, Manager Level 3.
QuickBaseCoachD
7 years agoQrew Captain
I agree. It depends on the required scale. If you have over a few hundred employees, then recursive is the way to go.