Alrighty, here is a "better" description of what I am working on.
what I am actually tracking are "overtime periods" or what we refer to as AFTPs. not every AFTP is going to have a flight attached to it. my thinking was that it is better to break those into separate tables, since there won't be a "flight" every time some does and AFTP. Similarly, there is a separate table for "LeaveTaken" that tracks when someone would need to take leave to do an "overtime period" (long story, its a government thing *rolls eyes*). Also, not every overtime period is going to have a remark attached to it, so again, my thinking was to break those not-necessarily-recurring things into separate tables to avoid a decent degree of "blank space" on the main table.
the reason I have referential integrity enforced is to take advantage of cascading deletes/updates: if an AFTP is deleted from the main table or updated, I would want any information regarding flights/leave/remarks to go with it.
Is this the best way to go? (obviously no, huh?)
and, in the case where an overtime period is input where there IS a flight related to it, what is the best way to handle creating a new record?