Firstly, rather than having your primary key in each table called ID, give it a name that reflects the table: DepartmentID, EmployeeID, etc.
Secondly, the department field in your tblEmployee could be a number field and linked to tblDepartment's DepartmentID making a one-to-many relationship as one department can have many employees.
Again, the tblVacation can have a VacationID rather than ID and this can have the number field EmployeeID linked this time to the primary key in tblEmployee as one employee can have many vacations.