Posted by calan on 09/22/05 00:33

<snip>

> What is the purpose of all these input tables?

This is basically an engineering configurator for a very complex product.
Each input table holds data for a specific "component" of the product.

Using the analogy of a car, a table called "Interior" may have fields such
as "Seat Color", "Stereo Type", "Number Of Speakers", and maybe tens or
hundreds more... A Suspension table could have "Wheel Size", "Spring Type",
"Load Rating", "Brake Type", etc etc.

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 in one table to say the
least... Also, I need the ability to work on individual components with
seperate apps, so the multiple table approach seemd to make sense.

I'm always open for suggestions though :-)

Thanks

• Next in forum: Re: Renaming a Server
• Prev in forum: Re: Syntax to add records if primary key = list
• Thread view: Re: searching a list of tables, derived from another table

[Reply to this message]