Share this Page URL

Chapter 2. The Basics of Database Design > Planning and Designing the HelloWorl... - Pg. 46

The Basics of Database Design 46 As you'll learn more about in Chapter 4, Access includes a tool known as the Database Splitter, which divides a database for you, putting tables in one .mdb file and any forms, reports, and other objects in a separate file that is linked to the tables. In Chapter 4, we'll split the HelloWorld database and use a front-end/back-end architecture for the rest of the book. Identifying the Tables and Fields for Your Database As you define the requirements of a database, you'll specify the principal subjects the database will store information about. These subjects might include something physical--an employee or a pro- ductor something more abstract, such as an order or a financial reporting period. Each table in your database should contain data about one subject. Use the list of requirements you've gathered to start identifying the subject for each table and the fields each table will contain. Let's pull together some of the concepts we've covered so far in this chapter by expanding the HelloWorld database we began in Chapter 1. As mentioned, this database tracks data and pro- cesses used in the launch and coordination of international marketing campaigns. As we develop the database in later chapters, we'll use the product and customer data in the Northwind sample database as the focus of the promotions, creating relationships between tables in the HelloWorld database and tables in Northwind as we need to. For the marketing campaigns database, we need to break down the requirements described earlier in this chapter into tables and fields. Table 2-1 provides some analysis of these requirements that we can use as the basis for designing the tables and fields. Table 2-1. Marketing Campaign Requirements Requirement Be available over a worldwide network. The database will be Design Implementation We addressed this requirement in the previous section. We'll use