interface quickly. If you are building a web-based solution, prototype web pages
can be built and then retargeted to the upsized enterprise database.
If you would like more in-depth information on building forms and reports
in Access, see Access 2002®: The Complete Reference by Virginia Andersen
(McGraw-Hill/Osborne, ISBN: 0-07-213241-8).
Sample Database Design
Now it’s time to build a real database design in Access. Our sample data domain
will be automotive-related data. The task is to build a database that will store make,
model, and year data for all of the automobiles on the market.
Designing the Data Structure
The primary goal for the database is to be able to retrieve a listing of automobiles
by model and retrieve applicable data about the particular model. Here are the
“facts" about the data that need to be incorporated:
¦
Categories define groups of like automobiles (e.g., SUV, Compact, etc.).
¦
Categories can be made up of subcategories (e.g., Sedans: Compact,
Luxury).
¦
Automobiles can be classified in only one category.
¦
Automobile models have a maker (e.g., Lexus
.
, Honda
.
,GMC
.
, etc.).
¦
Automobile models have a fuel efficiency rating (e.g., miles per gallon).
¦
Automobile models have a set of color options (e.g., Stardust Red, Baby
Blue, Forest Green, etc.).
¦
Automobile models have a manufacturing year.
Given these facts, we can come up with a database design to capture the data.
The data breaks down into three major entities as follows:
¦
Models Stores the fact data for the car model.
¦
Makes Indicates the manufacturer of the model.
¦
Category Defines the categorization structure for classifying or grouping
the models.
CHAPTER 2: Designing and Prototyping Enterprise Databases with Microsoft Access
21
Win&Mac / Microsoft Office Access 2003 Professional Results / Jerke / 222965-9 / Chapter 2
P:\010Comp\Win&Mac\965-9\ch02.vp
Wednesday, August 06, 2003 10:03:23 AM
Color profile: Generic CMYK printer profile
Composite Default screen
|
|