Still waiting on that plain english explanation of what you're doing. I have plenty of ideas but at this point would be guessing.
Still waiting on that plain english explanation of what you're doing. I have plenty of ideas but at this point would be guessing.
I am trying to build new combinations, like a Lego. For example you have one initial combination already existing with you and you want to build a new one. You take a NEW main part and build a new combination using existing parts.
Okay. Then are you generally always working the same lists of MachineSystems, MachineSubsystems, and Components?
Can a single distinct Component be linked to multiple distinct Subsystems?
What is the purpose of the master data table? Is there ONE record in the master data table for each combination?
Are the components the real "nuts and bolts" of this? Are the Systems and Substems just groupings of Components for convenience ?
Yeah, Generally working with the same list of MachineSystems, MachineSubsystems, and Components but I can create new ones as well, sometimes.
Yeah, a single distinct component can be linked to multiple distinct subsystems.
Apart from the four main fields i have many other fields. I have created a drop down for those fields so that i can link different records to different components.
Yeah components are real last level of hierarchy. you can call them "nut bolts". I did not understand your last question.
Can you elaborate a little more on "MasterData"? Is it just a table with extended information for each component? Should there be only one record of MasterData for each component and vise versa? Or is supposed to be multple MasterDatas for each Component?
The master data consists of a foreign key for components records. There are multiple records for each component and vice versa. That is why I have given a drop down for the other fields.