The Basics of Database Design A3: 73 Q4: A4: In general, it's considered poor design to store calculated values because you can produce the results you need through the imple- mentation of relationships and expressions. In practice, however, many databases do store totals and other calculated values for ease of reference. You need to balance performance and design considerations when creating your database. I'm converting a database I inherited to Access and keep getting errors when I modify the design of the tables. Should I just start over? One approach to consider is creating a new database file in Access and then importing the tables from the database you're converting without the data they contain. After making adjustments in the new database file, you can import the data. For details about importing data, see Chapter 4. After you complete this chapter: · To learn about using table and field properties to help manage data entry and refine the design of your tables, go to Chapter 3, "Managing the Consistency, Format, and Integrity of Your Data." · To learn more about entering data into a database, go to Chapter 4, "Importing and Linking to Data," where we describe how to import data from spreadsheets and other file formats into Microsoft Access. To learn about creating forms for entering and viewing data, go to Chapter 7, "Designing Basic Forms." On Your Own In this exercise, read through the requirements listed below, and then create the first version of the Tasks table, which we'll add to the HelloWorld database in Chapter 4. You can find a completed version of this table in the Workflow database in the Chap02 folder. In the HelloWorld database, we need a table that stores data about the tasks involved in coordinating each marketing campaign. We want to describe each task, assign the task to an employee to com- plete, know when the task is scheduled to start and end, and know whether the task is complete. We want to know the status of each task and be able to assign a priority to a task so that we can juggle and reassign tasks if necessary. We also want to know how much time was spent on a particular task. 1. 2. 3. 4. Create a blank database in Access, and then name the file Workflow.mdb. Create a new table, and add the fields necessary to meet the requirements described in the paragraph above. Select the data type for each field, and enter a brief description if you want. Designate a primary key for the table. With which tables would the Tasks table need a relationship?