Database Design Relationships

[Guest]

I am trying to create a database where I compare new technologies with
customer requirements. I have two tables, one for the technologies and one
for the customer requirements. I want to create a third table that defines
the relationship between the new technology and every requirement (high,
medium, low, none, negative). Do I have to create multiple records for each
technology, i.e. technology 1, requirement 1, 2, 3...n; ... technology x,
requirement 1, 2, 3...n, etc. etc.?

When I add a new customer requirement will I have to x number of new records
(one record for each technology) or is there an easier way to do this? Thanks!

 

[Allen Browne]

Yes. The junction table will have fields:
TechnologyID relates to a record in your Technology table
CustomerID relates to a record in your Customer table
Priority relates to a record in your Priority table
(high, ...)
so you can enter a record for every combination.

It might be more involved than that. For example, one customer might be
working on multiple projects, and the desired technologies might be specific
to the project rather than the customer, so the junction table would have a
ProjectID instead of a CustomerID.