I am designing a system for a client where they have carding wool weigh-ins throughout the day and also spinning ones. These can run for days and kept simple so the user can press a button it weighs the wool and then records the weight. The main information customer, shade etc will be duplicated, but they want both to run independent of each other.
I was going to create a form for each and combine on one large form as it will be running on a 24" touchscreen PC.
Regarding the structure, I was going to do a spinning table holding the main info for the spinning and a sub table of weight where each weight will be recorded, then when they start a new job a new spinning record will be created and then weights for that job will be created in the weight table and linked by job id.
My worry is do I create a Carding table exactly like spinning and link to weight table again, but keep the main part separate, to stop confusion or just create 1 table and have a type for spinning & carding then I don't have to duplicate the tables?
I am concerned with 2 forms open at the same time using the same tables.
I hope that make sense it's hard to describe.
Thanks
I was going to create a form for each and combine on one large form as it will be running on a 24" touchscreen PC.
Regarding the structure, I was going to do a spinning table holding the main info for the spinning and a sub table of weight where each weight will be recorded, then when they start a new job a new spinning record will be created and then weights for that job will be created in the weight table and linked by job id.
My worry is do I create a Carding table exactly like spinning and link to weight table again, but keep the main part separate, to stop confusion or just create 1 table and have a type for spinning & carding then I don't have to duplicate the tables?
I am concerned with 2 forms open at the same time using the same tables.
I hope that make sense it's hard to describe.
Thanks