These are the techniques I have used successfully, some of them for the past 25 years.Feel free to use this information if you think it will help you to develop your Access database.These table design guidelines are a requirement of a flexible and efficient database.Without these conventions the database can become bulky and difficult to support and maintain.After you have read the information below your are then ready to see how we exercise these designs in our Access query examples.Some of the concepts and recommendations presented in this discussion are my own and may not conform to 'text book instructions'.
The result of this rule is that the backbone of the database is independent of the data contained in the database.
Table Design examples for all aspects of Access databases can be found in this area of our website.
The goal of this table design tutorial is to provide information for beginning Microsoft Access programmers and future customers so that they will gain a basic understanding of relational databases.
From (1) above - Each field within a table should be dependent on the primary key field(s) and should be independent of all other fields in the table.
A generic example of a field that does not meet this definition is - when a field in your table contains values only some of the time based on some other field in the table or some event external to the table, then this field is not solely dependent on the main subject of the table.