Do you have trouble developing tables for your relational database? It can be confusing to determine which data should be in its own table, and what fields should be grouped together. To help sort out this challenge, consider each of the tables as nouns (Person, Place, or Thing) and each of the fields as adjectives (words that describe nouns).
Anything that is a noun should be its own table. For example, such typical tables are Customers, Orders, Products, Employees, etc. For those fields that describe these nouns, the fields should be included in the respective table.
Here are some examples of adjectives:
|Phone Number of the Customer||Customer Phone Number|
|Date of the Order||Order Date|
|Category of the Product||Product Category|
If the noun has many of the same adjectives, then you should consider making a table that can hold all of those similar adjectives.
Multiple Adjective Examples:
For more information, visit our page Microsoft Access and SQL Server Database Normalization Tips.
Thank you! Thank you! I just finished reading this document, which was part of a link in the recent Buzz newsletter. I have printed it for others to read, especially those skeptical on the powers of Access and its capabilities.