1. Build a database I: Design tables for a new Access database
Start with a plan
Before you start planning, remember a key fact:
Databases organize your information into separate tables, and each table contains unique data.
The database then uses relationships to join the data in the tables in a meaningful way.
That set of tables and relationships is called a relational structure, which the picture shows.
Here’s an example of the key fact: a table of asset data shouldn’t contain sales information, and a table of employee data shouldn’t contain medical records.
As the picture shows, the original spreadsheet places the data in one long list, while the database divides it into tables. In turn, the tables are related together in a way that lets you find information and extract meaning from your data.
Relational structures have several advantages over simple lists:
They reduce the amount of data that you enter and manage because you only store a piece of data once.
Reducing the amount of repeated data helps ensure accuracy, because you know you’re not counting an item more than once.
Relational structures make it easier to extract answers from your data. For example, you can find out which company supplies most of your furniture, or which computers have had the fewest support calls.
Build a database I: Design tables for a new Access database

2. Build a database I: Design tables for a new Access database
Decide on a purpose
The first step in planning a new database is to write down its purpose. In this case, you need to enter and manage your company’s asset data.
But don’t stop there. Ask yourself who will use the database and how they’ll use it.
For example, the technician who fixes a defective machine has different information needs than the accountant who tracks costs. Make sure your purpose statement addresses those different needs and uses.
Keep your purpose statement handy and refer to it as you design your tables. And don’t try to make the statement perfect, you can always change it.
Build a database I: Design tables for a new Access database

3. List the data you want to store
A good database design helps ensure your data is complete, and most importantly, that it’s accurate.
To reach those goals, start by listing the data you want to capture. You can start with your existing data — in this case, your spreadsheet.
Or, if you use paper ledgers or forms, gather examples of those. And don’t hesitate to ask your coworkers what they need.
Build a database I: Design tables for a new Access database

4. List the data you want to store
Another way to identify the information you need to store is to create a flowchart of the tasks associated with your data.
And while you’re at it, think about the reports or mailings you want to produce from the database.
Looking at the data you need to enter and consume can help you decide which data to store.
What tasks are associated with the data? For example, who will enter the data, and how? What kinds of forms will they need?
Reports or mailings: For example, do you want to know when desks and chairs need to be replaced? Who needs that information?
Build a database I: Design tables for a new Access database

5. Group your data by subject
As you list the data you want to capture, you’ll see it naturally falls into one or more subject matter categories or groups.
For example, your information may group itself like this:
Asset data, such as models, purchase dates, and costs.
Support data — who you call for help or spare parts. This category will probably include company names, addresses, phone numbers, and contact names.
Build a database I: Design tables for a new Access database

6. Group your data by subject
As you list the data you want to capture, you’ll see it naturally falls into one or more subject matter categories or groups.
For example, your information may group itself like this:
Supplier data, which looks a lot like support data because it includes companies and contact names.
Grouping is important because each category can correspond to a table, such as Assets, Support, Suppliers.
Build a database I: Design tables for a new Access database

7. Group your data by subject
Your groups may not result in a complete list of tables, but they’re a good starting point.
Just make sure each group contains unique data — just the asset information in one group, only the supplier data in another, and so on.
Build a database I: Design tables for a new Access database

8. Build a database I: Design tables for a new Access database
From groups, fields
The next step in your design is to list the fields for each table.
In an Access table, columns are called fields and individual records are called rows.
You plan your fields by deciding the specific information each of your groups should capture.
Again, you can refer to your existing data — the spreadsheet, a ledger, or even your card file. You can also open an existing database, such as one of the Access database templates, and see which fields it uses.
Build a database I: Design tables for a new Access database

9. Build a database I: Design tables for a new Access database
From groups, fields
For your asset database, you’ll probably want to list each item and information about each item, such as purchase dates and costs.
As part of this, try to reduce each field to its smallest logical component.
In a good design, a field represents a single piece of data, and the name of the field clearly identifies that data.
For example, your tables should have separate fields for first and last names because that makes it easier to find and sort your information.
Also, ask yourself if you need to record international data. If you do, you’ll need fields for Country, plus Region instead of State, and Postal Code instead of Zip Code.
Build a database I: Design tables for a new Access database

10. Build a database I: Design tables for a new Access database
From groups, fields
As you work, you may find yourself wanting to use data from one table in another.
For example, the picture shows that the Assets group includes fields for suppliers and support.
That’s natural — you’re seeing how you need to relate your tables, and we’ll discuss those relationships in just a bit. For now, include all the fields you think each table should have.
Note: If a field name contains more than one word, you can separate each word with spaces, but that may not be a good idea. Spaces can make it harder to create other components, such as Microsoft Visual Basic® for Applications code and a type of formula called an expression. If you need to use multiple words in a field name, you can eliminate spaces altogether, or separate each word with an underscore.
The Quick Reference Card that’s linked to at the end of this course provides more information about characters you can use in field names.
Build a database I: Design tables for a new Access database

11. Build a database I: Design tables for a new Access database
From groups, fields
As you work, you may find yourself wanting to use data from one table in another.
Finally, in case you’re wondering, you don’t plan rows. Those come naturally as you enter data in your fields.
Build a database I: Design tables for a new Access database

12. Build a database I: Design tables for a new Access database
Plan your primary keys
A final step in your plan is to add a primary key field to each of your tables.
A primary key is a field, or a combination of fields, with a value that makes each row in a table unique.
Primary keys are another way to avoid duplicating your data, because you can never duplicate a value in a primary key field.
Primary keys also enable relationships among your tables. That’s what makes your data powerful, because relationships allow you to ask questions and extract meaning from your data.
We’ll look at relationships in the next section.
Build a database I: Design tables for a new Access database

13. Build a database I: Design tables for a new Access database
Plan your primary keys
Access provides several ways to create primary keys.
You can use existing values such as part numbers, but only if each value will always be unique. Once you define a field as a primary key, Access never lets you enter duplicate values in that field.
Also, your key values should never change, because if they do your tables may become out of synch.
Build a database I: Design tables for a new Access database

14. Build a database I: Design tables for a new Access database
Plan your primary keys
Access provides several ways to create primary keys.
If your existing data won’t work as a primary key, you can use an AutoNumber field. Access simply increments the value in that field by one whenever you add a new record.
Build a database I: Design tables for a new Access database

15. Build a database I: Design tables for a new Access database
Plan your primary keys
So how do you plan primary keys?
Start by adding an “ID” field, such as “Asset_ID”, to each of your tables.
Or, if you want to use multiple columns of data to create a composite key, make a note next to each column you want to use.
The next course in this series, titled, “Build a database II: Create tables for a new Access 2007 database,” shows you how to create a primary key.
Build a database I: Design tables for a new Access database

16. A quick look at relationships
So, you’ve divided your data into tables and listed the fields and primary keys. How do you relate your data back together?
You create relationships by using the primary key field from one table as a field in another table.
The picture shows this. You can see how the primary keys in the Suppliers and Support tables have become fields in the Assets table. Those duplicate fields in the Assets table are called foreign keys.
This is a basic explanation of relationships; they’re covered in detail a later course in this series. Check back in the coming weeks.
Build a database I: Design tables for a new Access database

17. A quick look at relationships
At this point, you may be thinking, “Hang on, I’ve just duplicated some data!”
Don’t worry, this kind of duplication is okay. Primary key values are small, and you can’t extract meaningful information from your database unless you use them in relationships.
So, as a final step in your design, indicate your foreign key fields.
For example, the relationships in the picture allow you to answer questions such as, “Who supplied the monitors that we bought two years ago?”
If you need more information about keys, relationships, or database design, see the Quick Reference Card that’s linked to at the end of this course.
Build a database I: Design tables for a new Access database