hw 4 - 1. What are the steps you need to take in order to...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
1. What are the steps you need to take in order to design a database together with a brief explanation of each step? You do not need to use any database to explain your answers. These are the basic steps in designing a database: 1. Determine the purpose of your database. 2. Determine the tables you need in the database. 3. Determine the fields you need in the tables. 4. Identify fields with unique values. 5. Determine the relationships between tables. 6. Refine your design. 7. Add data and create other database objects. 8. Use Microsoft Access analysis tools. Determine the purpose of your database The first step in designing a Microsoft Access database is to determine the purpose of the database and how it's to be used. You need to know what information you want from the database. From that, you can determine what subjects you need to store facts about (the tables) and what facts you need to store about each subject (the fields in the tables). Determine the tables you need Determining the tables can be the trickiest step in the database design process. That's because the results you want from your database — the reports you want to print, the forms you want to use, the questions you want answered — don't necessarily provide clues about the structure of the tables that produce them. You don't need to design your tables using Microsoft Access. In fact, it may be better to sketch out and rework your design on paper first. When you design your tables, divide up pieces of information by keeping these fundamental design principles in mind: A table should not contain duplicate information, and information should not be duplicated between tables. When each piece of information is stored in only one table, you update it in one place. This is more efficient, and also eliminates the possibility of duplicate entries that contain different information. For example, you would want to store each customer address and phone number once, in one table. Each table should contain information about one subject. When each table contains facts about only one subject, you can maintain information about each subject independently from other subjects. For example, you would store customer addresses in a different table from the customers' orders, so that you could delete one order and still maintain the customer information. Optimize general table performance Determine the fields you need
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Each table contains information about the same subject, and each field in a table contains individual facts about the table's subject. For example, a customer table may include company name, address, city, state, and phone number fields. When sketching out the fields for each table, keep these tips in mind: 1. Relate each field directly to the subject of the table. 2.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/14/2010 for the course MIS 316 taught by Professor Kristine during the Spring '10 term at York University.

Page1 / 11

hw 4 - 1. What are the steps you need to take in order to...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online