Datasheet
๎ You can create queries that combine data from several tables to produce
information that is a composite of the information from those tables.
You might want to use this data to create form letters that include new
product information for products similar to those ordered in the past by
specific customers.
๎ You can easily create a query that includes only the orders placed by a
specific customer. This is a great tool if the customer wants a record of
all its orders in the several months or years.
Because queries are so important, I put information about them throughout
the book. In fact, Chapter 2 digs right in to give you a solid basis in queries so
that, when you create forms or reports, you know what your options are.
Queries, Forms, and Reports
Basics You Need to Know
In Access, all of your data is stored in tables. You can create totally self-
contained tables or relate multiple tables so that you can consolidate data
efficiently. Databases that work from a single, self-contained table are often
called
flat file databases. Databases that include two or more related tables
are called
relational databases. Fortunately, you use the same tools in Access
no matter which type of database you use.
As I mention earlier in this chapter, forms and reports are based on either a
table or a query. Queries can be based on tables or even on other queries โ
although queries based on queries can be kind of confusing to work with.
Access provides two primary methods of creating queries, forms, and reports.
You can start with a wizard, as shown in Figure 1-7, or you can create the
query, form, or report from scratch by using
design mode.
Whether you start with a wizard or in design mode, you begin the process of
creating a query, form, or report by choosing the table (or tables) you want
to use, and then you choose which fields to include. Remember that you can
also choose an existing query in place of a table.
In most cases, you can choose as many or as few fields as you like. You are
likely to find that some fields in a table (or query) are simply unnecessary.
For example, if you want to create a report that summarizes the values of the
items in your collection, you donโt need to include the field that tracks when
you received each item.
20
Part I: Accessing Both Ends: Getting Data In and Info Out
05_046593 ch01.qxp 11/27/06 1:23 PM Page 20