Odeh,
There is a very easy answer to this question. The CostPerUnit field
should not be in the TBLRECIPEDETAILS table. I suggest you remove it.
(Same for the Ingredient field, for that matter.)
It is a fundamental principle of database design that each value should
be stored one time, in one field, in one table. You are flouting this
rule with your setup.
Just leave the CostPerUnit in the TBLINGREDIENTS table. You can easily
retrieve this value, whenever you need it operationally for your forms
and reports and calculations, via a query or in calculated controls.
And then, if the price changes, no need to mess around with updating
data here and there.

Signature
Steve Schapel, Microsoft Access MVP
> Imagine this:
>
[quoted text clipped - 42 lines]
>
> Thank you!!!!