Microsoft Access Big City Store Sales Database CUSTOMERS First Last Address City State Zip PRODUCTS Product Supplier Description Units Cost Price SALES.

Slides:



Advertisements
Similar presentations
© 2007 by Prentice Hall (Hoffer, Prescott & McFadden) 1 Joins and Sub-queries in SQL.
Advertisements

Microsoft Office Overview Microsoft Word b Word Processor Create letters, reports and forms.
Alternative Database topology: The star schema
MS-Access XP Lesson 2. Input Mask Property 1.Field : Phone No Data Type : Number Input Mask : Character 0 represent a single digit and phone.
COMP 3715 Spring 05. Working with data in a DBMS Any database system must allow user to  Define data Relations Attributes Constraints  Manipulate data.
W.E. McCarthy JANE’S JELL-O DATABASE Employee (SSAN, Name) Purchase (Pur Invoice #, Date, *Supplier #, *Emp. SSAN) Supplier (Supp #, Name, Ind.
Class Presentation: Normal Form By Wen Ying Gao CS157A Section 2 October 20, 2005.
© 2008 Prentice Hall Business Publishing Accounting Information Systems, 11/e Romney/Steinbart1 of 121 C HAPTER 16 Implementing an REA Model in a Relational.
Data Model Examples USER SPECIFICATIONS.
MIS2502: Data Analytics Relational Data Modeling
Database Relationships Objective 5.01 Understand database tables used in business.
Database Relationships Objective 5.01 Understand database tables used in business.
Food Recall System Pre Code System Design Layout Version 1.0.
LSP 121 Week 2 Normalization and Advanced Queries.
Relational Database Concepts. Let’s start with a simple example of a database application Assume that you want to keep track of your clients’ names, addresses,
MIS 2502 Business Rules BJ’s is interested in developing a new application. The database will track product, customer, and sale information. It will.
Prepare for Final 1-3. Perfect Pizza wants to install a system to record orders for pizza and calzones. When regular customers call Perfect Pizza on the.
Microsoft Access Understanding Relationships Academic Health Center Training (352)
BUS1MIS Management Information Systems Semester 1, 2012 Access: Creating a Database Week 6 Lecture 2.
RELATIONSHIPS Generally there are two main database types: flat-file and relational.
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
BTEC National Extended Diploma1 IT Systems Analysis and Design Entity Relationship Diagrams.
© Copyright 2002, L. M. Linson, may be freely used with this notice Practical Database Design “Structuring Your Tables” by Larry Linson, presented to the.
Customer Order Order Number Date Cust ID Last Name First Name State Amount Tax Rate Product 1 ID Product 1 Description Product 1 Quantity Product 2 ID.
© Copyright 2002, 2005, 2013 L. M. Linson, may be freely used with this notice Practical Database Design “Structuring Your Tables” by Larry Linson, presented.
Ratios and the Coordinate Plane Lesson After completing this lesson, you will be able to say: I can plot pairs of values that represent equivalent.
MIS2502: Data Analytics The Information Architecture of an Organization.
Microsoft Access Intro Class 6 Relationships.
1 CSE 2337 Introduction to Data Management Textbook: Chapter 1.
HSC IT Center Training University of Florida Microsoft Access Understanding Relationships Health Science Center IT Center – Training
Databases,Tables and Forms Access Text by Grauer Chapters 1 & 2.
INFORMATION TECHNOLOGY DATABASE MANAGEMENT. Adding a new field 1Right click the table name and select design view 2Type the field information at the end.
BUS1MIS Management Information Systems Semester 1, 2012 Access: Data Entry Forms Week 7 Lecture 2.
Forms and Subforms 5.02 Understand database queries, forms, and reports used in business.
Quiz questions. 1 A data structure that is made up of fields and records? Table.
* Database is a group of related objects * Objects can be Tables, Forms, Queries or Reports * All data reside in Tables * A Row in a Table is a record.
IS6145 Database Analysis and Design Lecture 10: Normalization of Data Tables Rob Gleasure
MIS2502: Data Analytics Relational Data Modeling David Schuff
QUERY CONSTRUCTION CS1100: Data, Databases, and Queries CS1100Microsoft Access1.
Order Database – ER Diagram Prepared by Bryan Borcher Spring 2014.
Microsoft Access CS 110 Fall Entity Relationship Model Entities Entities Principal data object about which information is to be collectedPrincipal.
HSC IT Center Training University of Florida Microsoft Access Relationships Health Science Center IT Center – Training
Database Relationships
Order Database – ER Diagram
Let try to identify the conectivity of these entity relationship
Sales Order/Sale Entry Form
Order Database – ER Diagram
Microsoft Office Overview
Rob Gleasure IS6125 Database Analysis and Design Lecture 11: Normalization of Data Tables Rob Gleasure
Database Relationships
Order Database – ER Diagram
Order Database – ER Diagram
MIS5101: Business Intelligence Relational Data Modeling
Microsoft Office Overview
Ratios and the Coordinate Plane
TEXAS SUPPLEMENT WAREHOUSE
Data Solutions- Karm Upadhyay Zoheb Khan Swati Shukla
MIS2502: Data Analytics Relational Data Modeling
5.02 Understand database queries, forms, and reports used in business.
Curtain Style QUOTATION Curtain Style
Order Database – ER Diagram
Database Relationships
Order Database – ER Diagram
RECEIPT [Receipt description]
Microsoft Access Understanding Relationships
SALES RECEIPT Downloaded from
INVOICE Downloaded from
[Payee Name] [Street Address] [City, ST ZIP Code]
DELIVERY RECEIPT DELIVERY RECEIPT No : Date : Customer
Database Management system
Presentation transcript:

Microsoft Access Big City Store Sales Database CUSTOMERS First Last Address City State Zip PRODUCTS Product Supplier Description Units Cost Price SALES Customer Product Date Quantity

Microsoft Access Big City Store Sales Database CUSTOMERS First Last Address City State Zip PRODUCTS Product Supplier Description Units Cost Price Jack bought: 2 Hats 4 Pairs of Socks 3 Pairs of Shoes Shoes bought by: Jack Johnson Jill Jones Jerry Jacks

Microsoft Access Big City Store Sales Database CUSTOMERS First Last Address City State Zip PRODUCTS Product Supplier Description Units Cost Price Many to Many Relationship

Microsoft Access Big City Store Sales Database CUSTOMERS First Last Address City State Zip PRODUCTS Product Supplier Description Units Cost Price SALES Customer Product Date Quantity Main Table Junction Table Main Table

Microsoft Access Big City Store Sales Database CUSTOMERS First Last Address City State Zip PRODUCTS Product Supplier Description Units Cost Price SALES Customer Product Date Quantity 1 One Customer can have many sales 1 One Product can be sold many times To set these relationships, the main tables must have primary keys.

Microsoft Access CUSTOMERS FirstLastStreet AddressCitySTZip JackJohnson123 South Main StGainesvilleFL32608 JillJones28000 SW 583 AveGainesvilleFL32597 JerryJacks2701 Wilson RoadGainesvilleFL32655 JohnJinks3243 SE 4th TerraceGainesvilleFL32684

Microsoft Access PRODUCTS ProductSupplierDescriptionUnitsCostPrice HatsHats, IncFeltEach$5.50$ 6.00 SocksSocks LimitedWoolPair$2.25$ 3.50 ShoesShoes Are UsWoodenPair$9.99$12.15 PursesBag for AllSilkEach$8.45$ 9.15

Microsoft Access SALES CustomerProductDateQty BIG CITY STORE SALES INVOICE Date Customer Name Customer Address Customer City, ST Zip ProductDescriptionQtyPriceTotal Name Address City State ZipProduct Supplier Description Units Cost PriceQtyDate

Microsoft Access SALES FirstLastStreet AddressCitySTZipProductSupplierAddressCitySTZipDateQty JackJohnson123 South Main StGainesvilleFL32608HatsHats, IncPO Box 123WaldoFL /24/021 Jack bought a Hat on 1/24/02

Microsoft Access CUSTOMERS Cust #FirstLastStreet AddressCitySTZip C1JackJohnson123 South Main StGainesvilleFL32608 C2JillJones28000 SW 583 AveGainesvilleFL32597 C3JerryJacks2701 Wilson RoadGainesvilleFL32655 C4JohnJinks3243 SE 4th TerraceGainesvilleFL32684 PRIMARY KEY No Duplicates

Microsoft Access SALES CustomerProductDateQty Name Address City State ZipProduct Supplier Description Units Cost PriceQtyDate Cust# FOREIGN KEY Duplicates allowed Primary Key in Another Table

Microsoft Access CUSTOMERS Cust #FirstLastStreet AddressCitySTZip C1JackJohnson123 South Main StGainesvilleFL32608 C2JillJones28000 SW 583 AveGainesvilleFL32597 C3JerryJacks2701 Wilson RoadGainesvilleFL32655 C4JohnJinks3243 SE 4th TerraceGainesvilleFL32684 SALES CustomerProductDateQty Product Supplier Description Units Cost PriceQtyDate Cust#

Microsoft Access PRODUCTS Prod #ProductSupplierDescriptionUnitsCostPrice P1HatsHats, IncFeltEach$5.50$ 6.00 P2SocksSocks LimitedWoolPair$2.25$ 3.50 P3ShoesShoes Are UsWoodenPair$9.99$12.15 P4PursesBag for AllSilkEach$8.45$ 9.15 PRIMARY KEY No Duplicates

Microsoft Access SALES CustomerProductDateQty Product Supplier Description Units Cost PriceQtyDate Cust# Prod# FOREIGN KEY Duplicates allowed

Microsoft Access SALES QtyDateCust#Prod# What do we use for a Primary Key here? One way would be to have an auto number: CustomerProductDateQty QtyDateCust#Prod# SaleCustomerProductDateQty Sale#

Microsoft Access SALES QtyDateCust#Prod# What do we use for a Primary Key here? Another would be to have multiple key: CustomerProductDateQty QtyDateCust#Prod# CustomerProductDateQty This would assume that a customer would not purchase the same product twice in one day.

Microsoft Access Jack bought Hats Sales Customers C1 - Jack C2 - Jill C3 - Jerry C4 - John Products P1 - Hats P2 - Socks P3 - Shoes P4 - Purses C1, P1, Date, Qty Jill bought Purses C2, P4, Date, Qty Jill bought Shoes C2, P3, Date, Qty John bought Socks C4, P2, Date, Qty

Microsoft Access Big City Store Sales Database CUSTOMERS Cust# First Last Address City State Zip PRODUCTS Prod# Product Supplier Description Units Cost Price SALES Customer Product Date Quantity 11