On base what I did read out from your posts, you need:
1. An Employee registry table, p.e. tblEmployees: EmployeeID, FirstName, LastName, WorkingFrom, WorkingTo,...;
2. Optionally, a calendary table, p.e. tblCalendary: CalDate, IsWorkday, ...;
3.a) A table for working time registering, p.e. tblWorktime: WTID, CalCate, EmployeeID, WorkStart, WorkEnd, BreakFStart, BreakFEnd, ... (when only a single entry for a worker on a day is allowed);
3.b) A worktime log, p.e. tblWorktimeLog: WTLogID, CalDate, EmployeeID, EntryType, EntryTime, ... (allows to register several work periods on same day, or being ill/on travel/on leave, etc.).
The form you are discussing belongs to point 3, and it looks like you are going for variant a.
In this case I think at 1st opening of database, an OnOpen procedure for application must generate missing rows into tblWorktime running INSERT query like (assumed tblWorktime.WTLogID is autonumeric, and you have tblCalendary)
Code:
INSERT INTO tblWorktime
cal.CalDate, empl.EmployeeID
SELECT
FROM tblEmployees empl INNER JOIN tblCalendary cal
WHERE
cal.CalDate >= empl.WorkingFrom
AND
(cal.CalDate <= empl.WorkingTo OR emplWorkingTo Is Null)
AND
cal.IsWorkday
AND
cal.CalDate Not IN (SELECT CalDate FROM tblWorktime)
User registers all movements on form based on tblWorktime. A possible design:
Single Main form based on tblCalendary, p.e. fCalendary, which by default activates the record for current date. You can have there a navigation combo to select any of earlier dates too, when you want to allow this for user;
A continous form like adviced by Ajax, p.e. fWorktime, as subform of fCalendary. Subform is linked to main form on source table fields [CalDate] in both forms. So a list of all employees at date active in main form is displayed;
User enters (current) time into any of controls linked to fields WorkStart, WorkEnd, BreakFStart or BreakFEnd. On leaving the record, the entry is saved into tblWorktime.