Hi Kim,
It seems to me it would be much less of a headache if you create separate tables for Garments and Orders.
In the Garments table, you will have columns Name (A, B etc.), Type (Sampling, Production etc.) and corresponding price for each pair of Name-Type. I recommend to create a column ID with meaningful description for each row which then makes the later lookup less painful.
Then in the Orders table, you can have Garment column which is a link to the above Garments table and Price column which is a look up to Garments table’s Price column. For each record you can select the associated Garment ID and then its Price will be populated automatically for you.
This kind of approach will help you to be more organised about your data thus scaling up would be easier.
Kind regards,
Alex
Hi Kim,
It seems to me it would be much less of a headache if you create separate tables for Garments and Orders.
In the Garments table, you will have columns Name (A, B etc.), Type (Sampling, Production etc.) and corresponding price for each pair of Name-Type. I recommend to create a column ID with meaningful description for each row which then makes the later lookup less painful.
Then in the Orders table, you can have Garment column which is a link to the above Garments table and Price column which is a look up to Garments table’s Price column. For each record you can select the associated Garment ID and then its Price will be populated automatically for you.
This kind of approach will help you to be more organised about your data thus scaling up would be easier.
Kind regards,
Alex
Thank you for your input Alex.
Taken your comment to heart think I need to start getting my data organised
