Class Schedule
21 Aug | intro
23 Aug | clients
28 Aug | servers
30 Aug | networks
04 Sep | basics lab
06 Sep | structural layer
11 Sep | presentational layer
18 Sep | working with layers
20 Sep | behavior layer
25 Sep | images & design
27 Sep | website lab
02 Oct | object layers
02 Oct | graphics
09 Oct | document markup lab
11 Oct | spreadsheets, formulas & functions
16 Oct | thoughts about data display
18 Oct | Fall Break
23 Oct | database tools
25 Oct | spreadsheets lab
30 Oct | relational databases
01 Nov | tables
06 Nov | relationships |
05.02 |
next session
08 Nov | input & output
13 Nov | SQL
15 Nov | complex queries
20 Nov | databases lab
22 Nov | Thanksgiving
27 Nov | presentation design
29 Nov | presentation delivery
04 Dec | presentation lab
13 Dec | 0800-1100 | final in class presentation
This work
is licensed under a
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
home & schedule | class blog | syllabus | contact | grades
Relate your tables by ensuring referential integrity between Primary Keys and Foreign Keys.
Use the lookup wizard on the Foreign Keys to allow the program to create the relationships for you.
These do not have to be turned in, but they will be needed during the subsequent sessions.
You will need to decide whether or not you need to create a one-to-many or a many-to-many relationship between the Orders table and another table
Let's establish some rules for this database that may assist in deciding the relationships
Mr. Pitt, our client, wants to be involved in every purchase order for his library, but he doesn't like to think about complex things
However, you only have to do this in regards to the Order table. You must decide what field in the Order table is the FK and what PK in another table it should be related to
Your task is to decide on the relationship and link the related fields
but in Access you must create the many-to-many relationship by creating an intervening table and relating the Book and Author tables to it as two separate one-to-many relationships
The intervening table has its own Primary Key for each new record and also contains copies of Primary Keys of the two related tables, inserted in the intervening table as Foreign Keys
this intervening table will allow the two original tables to relate to each other in a Many-to-many relationship