databaseLessons

Tips for MS Access users

27
Aug
2008

Relational Database Design Guidelines

by manxman

While designing a relational database, it is a good idea to distribute the information in multiple tables. It is not advisable to store all the information in a single table, although it is easier to design. When your database grows in size, the efficiency decreases accordingly.

To read the rest of this article, Relational Database Design Guidelines - an introduction.

One Response to “Relational Database Design Guidelines”

  1. Millie Hilts Says:

    I do enjoy your articles. I’m afraid I know enough to be dangerous, but not enough to build the database that my company needs. We have a functioning one now but as you probably know, things change over time and we have to accommodate those changes in our program. Since I am not many years away from retirement, it seems foolish for me to pursue this new career - but I am totally hooked. I love getting into Access and doing the things I have learned on my own. The individual who originally wrote the Access database program that we are using should have taken the time to read articles that are available from sites like yours. Perhaps then it would be more change friendly and I could figure it out. It really needs to be rebuilt, as it is cumbersome and not even user friendly. However, I think at this point I will continue to do the “fixes” required and leave the rest alone.

    Thank you for your articles, I for one truly do appreciate the added knowledge.

Leave a Reply