to be clear, you should be using the primary key/foreign key as your link between tables, there is a very limited set of circumstances where I would store anything but a primary key/foreign key value. When the primary key is an AUTONUMBER (which I think all of your tables are, this is a good thing) the corresponding foreign key field in any other table should be LONG INTEGER, *NOT* text. Secondly, I would suggest maintaining consistent field names. For instance if you have an ingredient table I tend to label them something like I_ID (first initial of table, followed by _ID) then use the I_ID field name in all subsequent tables where you are referencing your ingredient table. It'll make things much, much, much easier for you to see where your links are broken. I also tend to suggest you put a prefix on all your objects to make it easy to discern where to go in case of a problem i.e. tblIngredient, qryIngredientSublist, frmIngredient (Data entry screen for tblIngredient), etc.
what I would have is something like
Code:
tblIngredient
I_ID I_Name ---> ingredient related fields
1 Eggs
2 Flour
3 Yeast
tblRecipe
R_ID R_Name ----> other recipe related fields
1 Bread Version 1
2 Bread Version 2
3 Bread Version 3
tblRecipieIngredient
RI_ID R_ID I_ID I_Qty ---> other recipe specific ingredient fields
1 1 1 5
2 1 3 10
3 1 2 1
tblJob
J_ID R_ID J_Multiplier J_Date ----> other job related details
1 1 3 1/1/2019
2 1 5 1/2/2019
EDIT (forgot this)
tblJobIngredient
--this would contain the ingredient items from the recipe along with whatever other fields you needed per ingredient per job
the multiplier on the job could be used to multiply out the base recipe by whatever factor you want (I know it's not that simple in baking but you get the idea)
Finally when you 'save' your job, force an append query to run to add all ingredients related to the selected recipe to be added to the specific job.