Can you have too many tables?

[Jeanette]

I have an access data with 15 tables. Because my program has projects that can have several different situations per project, I have to create several many to many tables. My question is can a database have too many tables? It appears that I have to create yet another table with a one to many relationship.

 

[Pat Hartman]

I've designed systems with 150 tables so 15 doesn't sound excessive. However, adding new tables should not be a regular occurance once your db is designed. Make certain that you actually need a new table, that you can't use an existing one by simply adding a code field to it. For example, if you were creating a system to track PC's and software, you might think you need two tables, one for software and one for hardware. You probably don't.

 

[Jeanette]

How many tables are too many?

I may have to create a new table this time around because I have discovered that contractors and borrowers can have many different names for companies but have the same address and telephone number. Right now I have a Borrower/Contractor table with a field for company name. I do not want to have to create a new field everytime there is a new or different company name. This has happened in the past where situations come up where I am forced to create a new one to many table because of unforeseen situations. Thanks for your reply to my last posting.