Requiring the employee to make entries as they move from control to control
has nothing to do with whether or not your form is bound to a table.
That would be accomplished by using code in your control's exit events or
enter events. Probably a bad idea unless you really want to force them to
enter data in exactly the order you require. (In my opinion)
Unless you are a very advanced Access developer, step back and start from
the beginning. You are trying to build an aircraft carrier when you've
never even build a dinghy.
Build a form based on your table (or a query). If you require the data in a
particular field, set it as required in your table. Once you do this, and
use it a time or two, then you can start tweaking the form.
(In my opinion)