Forum Discussion
MarkShnier__You
Qrew Legend
6 years agoI have done apps like that for costing purposes of the assemblies.
You can have a table related to itself, and that can allow you to build say a Tier 2 Assembly out of other Assemblies and perhaps also some extra components.
Then you can use that in a higher level Assembly and if you go high enough, I guess eventually you would have the whole car.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
You can have a table related to itself, and that can allow you to build say a Tier 2 Assembly out of other Assemblies and perhaps also some extra components.
Then you can use that in a higher level Assembly and if you go high enough, I guess eventually you would have the whole car.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
NathanielHammer
6 years agoQrew Cadet
I also mentioned creating a work-order to create such smaller components. The best Example I can give is the same place where I am stuck in my app.
The electrical department builds our Control Panels with a work order.
The work-order tells them the amount and type of components to use.
- I have a table of all the electrical components, part numbers, price, mfg etc.
- I have another table that allows my electrical supervisor to create a work order. The form leads him to select the different options that a control panel can have and how many of each he wants in it.
Currently these two tables are unrelated. How do I go about getting every component to be related in the work order dependent on the type of component it is? I don't want any 'Ethernet switch' component to show up when I ask him what 'PLC' he wants to use.
I have to do this component selection process for about 35 fields in the form.
------------------------------
Nathaniel Hammersmith
------------------------------
The electrical department builds our Control Panels with a work order.
The work-order tells them the amount and type of components to use.
- I have a table of all the electrical components, part numbers, price, mfg etc.
- I have another table that allows my electrical supervisor to create a work order. The form leads him to select the different options that a control panel can have and how many of each he wants in it.
Currently these two tables are unrelated. How do I go about getting every component to be related in the work order dependent on the type of component it is? I don't want any 'Ethernet switch' component to show up when I ask him what 'PLC' he wants to use.
I have to do this component selection process for about 35 fields in the form.
------------------------------
Nathaniel Hammersmith
------------------------------