General discussion

Locked

Access Relational Databases

By donna ·
Does anyone have a technique for explaining the relationships among tables for beginning database students?

This conversation is currently closed to new comments.

19 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Access Relational Databases

by Antsu In reply to Access Relational Databas ...

I've tried to play domino with tables. List field names of the table on little slice of paper. Start with one slice (table) and try to find another slice (table) which has common field. Then add slices (tables) and you can simulte different star schemas and relationships.

Collapse -

Access Relational Databases

by donna In reply to Access Relational Databas ...

The question was auto-closed by TechRepublic

Collapse -

Access Relational Databases

by tbangs In reply to Access Relational Databas ...

Donna:

I use the analogy of how people meet, find something in common and then can talk to each other. It's simple and they get it. It is best for beginning database students not to go into too much detail. When you start with basic queries, the lightbulbs start to go off.
Hope this helps a bit.
Terri

Collapse -

Access Relational Databases

by donna In reply to Access Relational Databas ...

The question was auto-closed by TechRepublic

Collapse -

Access Relational Databases

by bev In reply to Access Relational Databas ...

I show them a large table with the following fields names (abbreviated on the table)

FName
LName
Job title
DOB
Salary
Company car yes/no
Make of car
Car Reg
Year of car
Date of last service
Garage used

Get them to undestand this infois all related but table too big and the Date of service will only except one entry and Garage field would get messy (I'm sure u get the picture)

So we seperate it out into 3 tables
1)FName, LName, Job title, DOB, Salary, Company car yes/no

2)Make of car,Car Reg,Year of car

3)Date of last service
Garage used

Explain common denominator needed
Add Employee ID field to tables 1 & 2. I've found if u put the fields you're going to use for the relationship at this point and not at thebeginning - and that they add the same field to both tables pretty much at same time they understand why they are doing it

Then I encourage them to work out what common denominator would be good to link the table 2 & 3 together - already got reg no so why not duplica

Collapse -

Access Relational Databases

by donna In reply to Access Relational Databas ...

The question was auto-closed by TechRepublic

Collapse -

Access Relational Databases

by saratogapete In reply to Access Relational Databas ...

I think you have to establish the experience of your audience first. Here are two topics I talk about.

Excel
Most users have an Excel view of the world. They think Excel is a database. So I talk about how they have to repeat lots of information, row by row, in order to have a complete "record" about something.

L.L. Bean
Everybody has called L.L. Bean (or Land's End or Eddie Bauer), so I run through the scenario about you giving them your phone number or customer id. And then the repbrings upyour information and she asks you for your order. You order 2 sweaters, some boots, and a tent. (Then I ask the question) Which do you think would be the better way to store the information - To copy your address information over, and over, for each product you ordered or to save it once and then "access it" with a unique number?

It seems when I present it that way, they get the "goal" of trying to store data efficiently. Because what you are really trying to explain is a normalized database desig

Collapse -

Access Relational Databases

by donna In reply to Access Relational Databas ...

The question was auto-closed by TechRepublic

Collapse -

Access Relational Databases

by drexciya In reply to Access Relational Databas ...

The way I treat this subject in an Access course is first explaining a modelling technique, the ER model.

Making relational databases is like building a house; you need a construction drawing.

That's where the ER model kicks in. You simply putdownwhat the database will be about (take a generic example) and lo and behold, you end up with >1 table. Then you'll fit them together with relationships.

Then explain why you're doing this --> increased efficiency, increased accuracy and less input.

Collapse -

Access Relational Databases

by donna In reply to Access Relational Databas ...

The question was auto-closed by TechRepublic

Back to Windows Forum
19 total posts (Page 1 of 2)   01 | 02   Next

Operating Systems Forums