Recitation02_for Access 2007

Recitation02_for Access 2007 - ORIE 3120 Industrial Data...

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

View Full Document Right Arrow Icon
1 2/2/2010 ORIE 3120 Industrial Data and Systems Analysis Recitation 2 Advanced Relational Database Concepts Basic Concepts 1. You must have completed Recitation 1 before attempting this recitation. 2. Your teaching assistant will explain or review the following concepts: Throughput, yield loss, speed loss, line transitions Getting Started 1. You will turn in this document at the end of recitation to receive credit for attendance. If you are working in teams, list the names and NetID’s of you and all your team members. Name NetID (ex. pj16) 2. Create a directory to store your work. If you use the lab machine, be aware that the directory (and all your work) will disappear when the machine is rebooted. We recommend using a USB flash-drive. 3. Open Microsoft Access (MS Access). It is one of the Microsoft Office collection of programs. 4. Create a blank database and save it in your directory. Give it a unique name by combining your NetID with the identifier for this recitation: ex. “pj16REC02.mdb.” We will refer to this database as your working database. 5. Write down the file name here: ___________________________________________ 6. From the course website, download the following file to your directory: “THRUPUTHistory.mdb”. 7. Return to MS Access. Link all tables in “THRUPUTHistory.mdb” into your working database. (Recitation 1 explained how to link tables.) Relational Database Design In a relational database, you should store information in the most efficient way possible. That is, you want to minimize the duplication of information in a database. For example, suppose you are logging phone conversations with a customer. When talking to me, you might sometimes log my name as “Peter Jackson”, or as “PJackson”, or as “Jackson, Peter”. When you want to analyze the log, you will have difficulty identifying that all those entries identify the same person. It would be better to have a separate table of customers with a unique identifier for each customer. That way, I would be in the table of customers exactly once, say as Customer ID: 007, Name: Jackson, Peter. Then, in the log file, every time you talk to me, you log it as a conversation with Customer ID 007. The database “THRUPUTHistory.mdb” uses this approach. There are separate tables to describe clock codes, problem types, shift names, product names, and workcenter types. Each row in each of these tables has a unique identifier. [Hint: Design view, key]
Background image of page 1

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

View Full DocumentRight Arrow Icon
2 2/2/2010 1. What is the unique identifier for the table “ShiftNames”? __________________ 2. What is the unique identifier for the table “ClockCodes”? ___________________________________________________________ The two history tables refer to these data using unique identifiers. 3.
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 02/09/2012 for the course ORIE 3120 taught by Professor Jackson during the Spring '09 term at Cornell.

Page1 / 15

Recitation02_for Access 2007 - ORIE 3120 Industrial Data...

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