Haven't experienced this error, but a similar one. You don't really say which table the combos are bound to (e.g. ItemID is in 3 tables) but I suspect your issue is that you're trying to pick child values (the many) before you pick the parent value (the one side of the relationship). So I think Items.ItemID is the last combo. Also thinking that your form is based on a multi-table query which can raise this problem. In that case, changing your query join(s) to outer joins might help. A better approach may be a main form with subform(s).
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Not really. You could potentially use different query joins as long as they don't violate any relationships you've defined.Ive tried changing the joins in the relationships but still getting the error. is this the same as query joins?
I'm not following why the controlsource (or are you saying recordsource?) for 3 combos are from the same table or query. The behaviour in your 1st post suggests the combos are bound (have a controlsource) yet you say you're filtering. You don't bind filtering combos. Nor would you ever pick the Primary Key (ItemID) from a combo (unless maybe it is meaningful data instead of an autonumber ID).
Maybe all you have to do is remove the controlsource property to eliminate the error, but that still leaves me confused about the other things. So are you filtering records or creating/editing them?Responsible Technicican > Category > ItemID
Can you copy db, compact, zip and post the copy and include instructions on how to replicate?
Last edited by Micron; 09-28-2021 at 10:58 PM. Reason: clarification
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.