I looked at your dB last night and also wasn't able to understand your problems. I did see several things that should be addressed. (just my opinion)
These are not in any particular order.... I am doing this from memory.
You have linked the tables on the PKs. (Employees.ID <-> Time Off.ID) This results in a one to one relationship. (probably not what you wanted)
----------
Which brings up ...
In every table the PK is "ID". At the very least, this can be confusing. Take the time to create useful field names.
For instance, you could use "Emp_ID", "EmpID_PK" or "EmployeeID" as the PK for the employee table. For the Time Off table, might use: "TimeOff_ID", "TimeOffID" or "TimeOff_PK". For the corresponding field in a linked table, you could use the suffix "FK". So if the time off table is linked to the employee table, the field names might be:
Employee table
EmployeeID_PK
TimeOff table
TimeOffID_PK
EmpID_FK (link to employee table)
This would be a one to many relationship... one emp can have many time off records.
----------
There should be NO spaces or special characters in object names... except the underscore.
----------
You have lookup FIELDS in the tables. No experienced developer that I have heard of uses lookup fields.
See:
The Ten Commandments of Access ->>
http://access.mvps.org/access/tencommandments.htm
The Evils of Lookup Fields in Tables ->>
http://access.mvps.org/access/lookupfields.htm
----------
This will be easier to fix once the field names/type are corrected. You have the "points" as Text instead of Single. You can do calculations on "Text" numbers but you have to go through a lot of conversion/validation to do the calculation. Easier to just fix the fields.
I would suggest re-evaluating your table design/structure.