It appears that you are confusing "record" with "layout". You can show data from events on an employee layout and data from the employee table on an events layout using relationships.
But the exact type of relationship involved is key.
Am I correct that for an event, there can be more than one employee associated with that event? And a given employee can be associated with more than one event?
I can have 20 guys working 1 event and or one guy working multiple events the same day. one employee will work multiple events throughout the week.
Then you have a many to many relationship and you cannot link an employee directly to an event. You need to add an additional "join" table to link employees to events.
And I will repeat the comment that I posted in an earlier thread that I see no need for more than a single ID field in your relationships. What you have appears to be redundant and a needless complication.
Employees::__pkEmployeeID = Employee_Event::_fkEmployeeID
Events::__pkEventID = Employee_Event::_fkEventID
You can place a portal to Employee_Event on the Employees layout to list and select Events records for each given Employees record. Fields from Events can be included in the Portal to show additional info about each selected Events record and the _fkEventID field can be set up with a value list for selecting Events records by their ID field.
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
And I happen to have a many to many demo file that links contacts (think employees) to events: https://www.dropbox.com/s/oyir7cs0yxmbn6i/ManyToManywDemoWExtras.fp7
It's in the older file format, but FileMaker 12 or newer users can use Open from FileMaker's File menu to open this file and produce a copy converted to the .fmp12 file format.