Thread: Database table and relationship advise

I really hope someone can help me as I seem to be going around in circles at the minute.
I am a sort of newbie to access, but have set up databases in the past (although it’s a while and my skills are very rusty to say the least).

I need to set up a database that records issues for the production WorkCentre’s.
This data will then produce a report that will be used as the communication log between the shifts.

The next part is that for only 2 WorkCentre’s I need to record issues and measurements.

The flow is as follows:
Everything links back to the Job number & Product number.
From that you will have a mill roll number and then you may have multiple batches for that mill roll.
For each batch you may have up to 8 lanes (but this could be from 1 lane to 8lanes – varies from Product to Product)

So this is what I have been thinking?
Have 1 table that will record all the issues?
Then from that using Job number as the link, have a separate table for each of the WorkCentre’s that have measurements.(The same measurements and information is not carried out in these work centres)

I do have a separate table for Batch data, but not sure if this the way to go??

I have attached how I think the data should be layed out, but please give me your taught and ideas.