I need to design a database which is contained the dyeing orders.
The following is the information about the dyeing orders.
Each order can contain many dyeing jobs.
e.g. Job A to dyeing red & white colours for some lot of cloth
Job B to dyeing blue for one lot of cloth and red for the other lot of cloth.
And Each dyeing job can have more than one dye task
e.g. Job A can dye red colour for a lot of cloth (Lot no: 12345)
Job A can dye red colour for two or more lots of cloth (Lot no: 12345, 12346, 12347,....)
Job A can dye red colour for a lot of cloth and blue colour for two lot of cloth (Lot no: 1111,1112)
Job A can dye red and blue for one or more lots of cloth.
And Each dye task can have additional sub-tasks for different dyeing progress for different lots of cloth.
Example for the Order
Order No : 12345 Customer : HK Company , Date : 12 August 1999
Job A : dye red colour & blue colour for three lots of cloth (lot1 weight 1200gm, lot2 weight 1300gm, lot3 weight 500gm)
red colour for 1000gm, blue colour for 2000gm
Additional sub-Tasks : Task1, Task2, Task3
Red colour cloth deliver to ABC Company
Blue colour cloth deliver to XYZ Company
Job B : dye red colour for two lots of cloth (lot4 weight 1000gm, lot5 weight 2000gm)
red colour for 2500gm
Additional sub-Tasks : Task1, Task3, Task5
Deliver to ABC Company

I have some ideas of fields of table.

OrderNo, CustID, OrderDate, Remarks,JOBID, DyeColourID, ClothLotNo, Sub-task, DeilveryAddress.
But it is many repeat groups (e.g. JOBID, DyeColourID, ClothLotNo, Sub-task)

Would anyone can help me to nomrailize this database and give the advise to design the data-enty form.

Thanks.

Dennis
dennischoy@hotmail.com