From 286c7aea398447a770986f82a01e53cc6e1f32b7 Mon Sep 17 00:00:00 2001 From: noah Date: Mon, 26 Sep 2022 15:58:16 -0500 Subject: [PATCH] Chaning README title --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e32965c..a544f46 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# Case Study 3 +# Exam 1 - Queen Anne Curiosity Shop ## Instructions - Answer Questions A through U found on pages 133-140 in Chapter 2 for the Queen Anne Curiosity Shop. @@ -70,4 +70,4 @@ S.) Show the LastName, FirstName, and Phone of all customers who have bought an T.) Show the LastName, FirstName, and Phone of all customers who have bought an Item named ‘Desk Lamp’. Use a combination of a join in JOIN ON syntax and a subquery that is different from the combination used for question S. Present results sorted by LastName in ascending order and then FirstName in descending order. -U.) Show the LastName, FirstName, Phone, and ItemDescription for customers who have bought an Item named ‘Desk Lamp’. Also show the LastName, FirstName, and Phone of all the other customers. Present results sorted by Item in ascending order, then LastName in ascending order, and then FirstName in descending order. HINT: In Microsoft Access 2016 you will either need to use a UNION statement or a sequence of two queries to solve this, because Microsoft Access disallows nesting an INNER join inside a LEFT or RIGHT join. The other DBMS products can do it with one query (not a UNION statement). \ No newline at end of file +U.) Show the LastName, FirstName, Phone, and ItemDescription for customers who have bought an Item named ‘Desk Lamp’. Also show the LastName, FirstName, and Phone of all the other customers. Present results sorted by Item in ascending order, then LastName in ascending order, and then FirstName in descending order. HINT: In Microsoft Access 2016 you will either need to use a UNION statement or a sequence of two queries to solve this, because Microsoft Access disallows nesting an INNER join inside a LEFT or RIGHT join. The other DBMS products can do it with one query (not a UNION statement).