The secret is in using mutiple occurrences of your data source tables Employees and Applications.
InterviewingEMPLOYEES::__pkEmployeeID = Applications::InterviewerID AND
CheckingEMPLOYEES::__pkEmployeeID = Applications::RefCheckerID
Will allow you to put fields from InterviewingEMPLOYEES on your Applications layout to show info abou the interviewing Employee. And you can place fields from CheckingEMPLOYEES on your Applications layout to show details about the employee assigned to check references.
The "boxes" found in manage | Database | Relationships are called "Table Occurrences" they represent specific tables defined on the Tables tab. To create InterviewingEMPLOYEES, you click the Employees box, then click the duplicate button (two green plus signs). You can then double click this new "occurrence" to open a dialog where you can rename it like I have.
This does not create a new Table. It creates a new reference to an existing table.
Note that this only permits you to assign one interviewing employee to a given application and only one reference checking employee to a given application. If you need to make multiple assignments for either of these tasks for a given application record, a different structure is needed.
To see the two lists all Applications for a given Employee in a portal, you can start with Employees as your layout's table occurrence, and link in two more occurrences of Applications, each linking by a different match field in applications.
If "Table Occurrence" is a new concept, you may find this tutorial helpful: Tutorial: What are Table Occurrences?
Ah...okay. I had it reversed.
I tried creating two additional references in the graph for Applications...not Employee (ApplicationsInterviewer - which defines InterviewerID->Employee::EmployeeID and ApplicationsRefChecker - which defines RefCheckerID->Employee::EmployeeID). Both of these went to the same instance of "Employee"
So there was no direct relationship between "Applications" and 'Employee" in the table graph...which meant I couldn't select anything in the portals when I tried this since there was no relationship.
I tweaked it and the above worked as I'd wanted.
Thanx for the quick response.