Can you send us a snap shot of the relationship.
The screen shot doesn't help enough.
You refer to the time table TO but none of the screenshot you posted refers to that??
So starting with simple questions, is the field type the same on both sides of your relationship?
Are there two records with matching values in the two fields??
yes they are the same type
not sure about the matching values
What is the purpose of the name code?
If your purpose is for a key to make relationships with, please don't use a key based on employees names. Good relational keys need to be two things: unique and immutable. People share first letters of first names, people share first letters of last names, and it's reasonable that you may eventually have a pair of employees with the same name code — not unique. People also change their names, which would change their name codes — not immutable. You're better off with UUIDs.
If the purpose is to help look-up employees quickly in a user interface, wouldn't a search based on full names be just as effective?