Posted by --CELKO-- on 10/01/21 11:27

>> If you have 100 components with maybe 30-50 configuration questions for each one..and then multiple products tied into the same system...... well.... you end up with a massive number of input fields [sic] in one table to say the least... <<

Have you thought about a using a parts explosion/tree model? All the
options would be subordinates under a component in a master model that
gets traversed and pruned as decisons are made. You are looking at a
tree with 5000 nodes and you can use the hierarchy to enforce some
dependencies. I.e. If you get a radio, then you have to pick from five
models, if you do not get a radio, we do not show the models.

• Next in forum: I tried these .....
• Prev in forum: bit off topic: street name database US
• Thread view: Re: searching a list of tables, derived from another table

[Reply to this message]