It sounds like you've enforced referential integrity, which would require that whatever you enter/choose in the injury type field in FAReport must exist in tbl_FAInjury already. Alternatively, you can use the not in list event of a combo to add it on the fly.
with the relationships you have structured, the message is telling you you cannot add a record to FAReport until all the fields linked to other tables have been completed with a valid value (i.e. one that exists in the relevant parent table. You cannot leave any of them blank - there may be others but the message is referring you to the InjuryTypeID
Hi,
I've removed enforce referential integrity and all works now. Is this likely to cause any problems?
Access no longer protects you from users entering whatever they want. You can end up with Acme Co, Acme Company, Acme Comp, etc.
So if my inputs are via combo - limited to list it should be ok?
Yes, though you face the same problem of the value needing to exist already, unless you add code to the not in list event. Searching here for "notinlist" should turn up the code if you need it.