Understanding table development
I am trying to understand the concept of one-one, one-many, many-many. This seems to be critical as you develop the structure of your database. I am not quite certain how far you take the concept….does each field need to be unique to that table? Here is an example.
I have three types of customers….individuals, schools & churches. All have similarities, i.e. an address, city, state, zip, phone, etc. I also therefore have the same three types of PROSPECTIVE customers – those that I am hoping will become customers.
Would I therefore create six tables to capture their unique data (name, address, city, state, zip, etc which is unique to that individual, church or school)?
Or, would I create two tables for this data (one each for customers & prospects)?
Or, lastly is it best to only have one table that had all of their unique data + one field with the variable data (customer or prospect)?