Let's do a little work to improve the field names. As in database design, naming conventions are, to some extent, a matter of personal preference. But you should be aware of some useful rules. A field name should appear only once in each database. In databases in which you have much contact information, you could have several tablesCustomers, Suppliers, Shippers, and so onthat have a field named Address. In the Classic TV database, this problem is less pronounced. But in Table 3.26, you still have duplicate fields, such as First Name and Last Name in the Actors and Roles fields.
A good way to resolve this duplication is to prefix each field with the name of the table. Some database designers like to include a table prefix for every field; others use the prefix only where they deem it necessary to avoid confusion with similar fields in other tables.
When field names get too long, a common practice is to abbreviate elements. Thus, a customer address in a Customers table becomes CustAddr, and the address in the Suppliers table is SuppAddr. Other Access experts disagree and prefer to use whole words throughout for completeness and clarity.
Here are a few important rules for naming fields:
In Table 3.29, I've renamed the fields listed in Table 3.26 so that they more closely conform to good naming practice and convention. The names do not represent some state of perfection; other (perhaps better) choices are possible.