4-12 CHAPTER 4 • CREATING AND USING QUERIES
1. Good database design and normalization rules preclude you from including a column of
extended prices in any of the Coffee Merchant invoice tables. Because the extended price is
the product of the quantity, unit price, and any applicable discount, it is calculated in the
query. It must not also be stored in the table. Why? What if we discover a mistake in the
number of units or unit price on one or more invoices? Changing either renders the extended
2. An outer join reveals “hidden” information that is not obvious when you observe any
individual table. Outer join queries can display customers who have not ordered anything
3. The relationship between tblStudents and tblClassRoster is one-to-many. There is no
particular problem in representing the relationship. If the tables were tblStudents and
4. Crosstab queries aren’t as powerful as pivot tables. While crosstab queries provide summary
facilities like totals, you cannot filter or sort on a calculated field. Pivot tables are crosstab
5. The Tables panel would contain tblCustomer and tblOrders, joined on their common column,
say, CustID. The query’s field row would contain FirstName, LastName, Street, City, State,
and OrderDate. Under the State column place the criteria “ID” (the two-character
abbreviation for Idaho). Under the OrderDate, in the same row as the state criterion, write the