Joins across customers, equipment, calls, technicians and parts produce six saved queries, including a parameter prompt, totals and an outer join, in IT163's Unit 7 set for the same service firm. Searches like "it 163 unit 7 assignment example", "it163 unit 7 sample" and "it163 unit 7 example" land here.
What a finished IT163 Unit 7 multi-table query set looks like
Six more objects join the Queries group. qryCallDetail runs through equipment to reach each customer's business name and builds TechName by joining first and last names with a space. qryCallsForTechnician prompts for a last name and a start and end date. qryPartsCostPerCall totals by CallID, summing quantity times unit cost. qryCallInvoice stacks on that result through a left outer join, so calls that used no parts still appear, computing LaborCharge from hours and ChargedRate and an InvoiceTotal that wraps the parts figure in Nz to turn blanks into zero. qryUnitsNotServicedThisYear pairs an outer join with an Is Null test, and qryCallsPerCustomer counts calls by business name. Design view shows arrowheads on both outer joins, and a two-page catalog records each query's join path.
How a IT163 Unit 7 example is structured
The set is ordered by join difficulty: plain inner joins first, then parameters, totals, a query built on another query, outer joins, and grouped counts. Every catalog entry states the row grain its output is expected to have, one row per call or one per customer, because grain is what exposes a bad join. The invoice query is deliberately built in two stages. Parts are summed per call first and only then joined back to the calls, since joining calls straight to part lines would repeat each labor charge once per part and overstate every invoice with more than one line. Parameter prompts are worded as questions a dispatcher would understand. Three invoice totals are worked by hand in the catalog and compared with the query output, and the unmatched-units result is checked against the equipment list it came from.
Grain stated before joining
Each query's catalog entry names what one output row represents, so a count that drifts above the number of calls signals a join problem at once.
Parameters worded as questions
Prompts ask for a technician's last name and a date range in plain terms, and the catalog notes what happens when a prompt is left blank.
Invoices in two stages
Parts cost is totaled per call before any join to labor, which keeps a three-part call from tripling its labor charge.
Outer joins that keep rows
Left joins preserve calls with no parts and equipment with no calls, and Nz turns missing sums into zero rather than a blank.
Totals checked by hand
Three invoices recomputed from raw rows and matched to query output, the evidence that the joins and expressions agree with the data.
Where marks go in IT163 Unit 7
Multi-table queries in IT163 are graded on whether their numbers are true, and the usual failure produces numbers that look fine. Joining calls directly to part lines and then summing labor inflates every invoice with more than one part, an error visible only when a total is recomputed by hand. Inner joins where the question needs every call drop part-free calls from the invoice list without warning. Missing Nz leaves blank invoice totals. An extra table dropped into the design grid with no join line multiplies rows into the thousands, and parameter prompts reading only Enter value leave users guessing. Totals queries grouped on too many fields return one row per record and summarize nothing. Unmatched queries with the Is Null test placed on the wrong table return an empty datasheet.
Get a IT163 Unit 7 example written to your instructions
Paste the questions your IT163 Unit 7 prompt poses, attach the database built so far or its relationship diagram, and add the rubric. Joins, parameters and totals are written to those questions in 24-48h, with a catalog showing grain and hand-checked figures. Your first custom sample costs nothing.
IT163 Unit 7 questions, answered
Why does my query show each call several times?
Because at least one table in the query holds several rows per call, usually a parts or line-item table, and every call row pairs with each of them. That is correct for a line listing and wrong for a per-call total. Summing the detail rows in a separate totals query first, then joining that result to calls, gives one row per call again.
What is the difference between an inner and an outer join?
An inner join returns only records with a match on both sides, so a call with no parts disappears from a calls-and-parts query. A left or right outer join keeps every record from one side and fills blanks where the other side has no match. Access marks outer joins with an arrow on the join line in design view.
Can a parameter query ask for more than one value?
Yes. Each bracketed prompt in the criteria row becomes its own question when the query runs, so one query can ask for a technician's name and then a start and end date. Access asks them in grid order from left to right, which is worth knowing when your instructions specify the order prompts should appear.