Five enforced relationships, one junction table with a composite key, and a written case for each cascade setting: the refrigeration firm's database takes its real shape in IT163 Unit 4. Searches like "it 163 unit 4 assignment example", "it163 unit 4 sample" and "it163 unit 4 example" land here.
What a finished IT163 Unit 4 relationships and keys exercise looks like
The .accdb now holds six tables, and its Relationships window is arranged parent to child from left to right: customers to equipment, equipment to service calls, technicians to service calls, then calls and parts both feeding tblCallParts. Every line carries the one and infinity symbols of an enforced one-to-many link. In tblCallParts, CallID and PartNumber share the key icon, so the same part cannot be listed twice on one call, and Quantity refuses anything below one. PartNumber is a natural key, Short Text sized to 12, holding supplier codes such as EVM-2210 for an evaporator fan motor. Alongside the file sits a three-page memo: a key inventory, a relationship table with integrity and cascade settings, and a log of four deliberate violations with the refusal each one produced.
How a IT163 Unit 4 example is structured
The memo is organized key first. Primary keys are inventoried before any relationship is discussed, and each is labeled surrogate or natural with a sentence on the choice: AutoNumber for customers, technicians, equipment and calls because nothing in the business guarantees uniqueness, a supplier code for parts because the supplier already does. Foreign keys follow, each matched in type and size to the key it references. Relationships are then described one at a time in a small table, and the junction table gets its own section because resolving a many-to-many link is the hardest idea in this stretch of the course. Cascade settings are argued individually rather than applied as a blanket choice. The test log comes last, serving as evidence that the settings actually behave as the memo claims they do.
Surrogate or natural, per table
Four AutoNumber keys and one supplier part code, each with the reason uniqueness can or cannot be trusted to the real-world value.
A junction table for parts used
tblCallParts sits between service calls and the parts inventory; its two-field key blocks duplicate lines while allowing many parts per call.
Matching types on both ends
Every foreign key is a Long Integer number facing an AutoNumber, or Short Text 12 facing Short Text 12, so enforcement is possible at all.
Cascade choices, argued singly
Cascade update on part codes, since suppliers renumber; cascade delete only from calls to their part lines; nothing else deletes downstream.
Four attempted violations
A call for a nonexistent unit, a customer deleted while owning equipment, a duplicate part line and a zero quantity, each refused and recorded.
Where marks go in IT163 Unit 4
Graders in this unit usually open the Relationships window first, and a crowded window with crossing lines and missing tables costs points before anything else is read. Foreign keys created as AutoNumber fields are the classic error: the child table then numbers itself and never matches its parent. Mismatched types, Short Text against Number, leave the enforce option unavailable, and some submissions quietly drop enforcement rather than fix the cause. A calls table carrying Part1, Part2 and Part3 columns instead of a junction table is a many-to-many problem disguised as a solution. Junction tables without a composite or otherwise unique key accept duplicate lines. Cascade delete switched on everywhere draws pointed comments, because removing one customer would erase years of service history. Missing rationale for keys loses the written portion outright.
Get a IT163 Unit 4 example written to your instructions
Whatever tables your section built in the previous unit, those are the ones this sample should relate. Send them or their field lists, plus the IT163 Unit 4 prompt and rubric, and expect keys, a junction table and the memo inside a working .accdb within 24-48h. There is no fee for a first custom sample.
IT163 Unit 4 questions, answered
Why can't the foreign key be an AutoNumber as well?
An AutoNumber generates its own values, one per new record, so a foreign key built that way would count upward on its own instead of holding the parent's ID. The foreign key has to accept whatever value points at the right parent, which is why it is a Long Integer number field matching the AutoNumber's underlying type.
When is cascade delete a reasonable choice?
When child records have no meaning without the parent. Part lines on a service call qualify: if the call is removed, its lines describe nothing. Service calls themselves do not qualify, because deleting a customer should never erase billing history. Most IT163 rubrics reward a sentence explaining each cascade choice more than the setting itself, so the reasoning is worth writing out.
What makes a composite primary key different from a regular one?
It uses two or more fields together, and only the combination must be unique. In a parts-per-call table, the same call appears on several rows and the same part appears on many calls, but any given pair appears once. That is exactly the rule the business needs, so a separate AutoNumber key would add a field without adding protection.