Access | Designing a database exercise | Creating a recipes database

This exercise is provided to allow potential course delegates to choose the correct Wise Owl Microsoft training course, and may not be reproduced in whole or in part in any format without the prior written consent of Wise Owl.

Software ==> Access  (66 exercises)
Version ==> Access 2010 and later
Topic ==> Designing a database  (3 exercises)
Level ==> Average difficulty
Subject ==> Access training

You need a minimum screen resolution of about 700 pixels width to see our exercises. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

Create a new database called Recipes.

Create a new table to hold the different supermarket areas from which you can buy ingredients.  When you have defined the fields, enter data as shown below:

Access 2010 exercise - Designing a database (image 1)

Your table should contain two fields, as shown above

Close this table down, then create another table called Recipe to hold your favourite recipes (if you haven't got any, make them up!).  Here is what this might look like:

Access 2010 exercise - Designing a database (image 2)

Here we will add the ingredients for two recipes, but feel free to choose different ones

Finally, create and populate a table to hold the ingredients that you need to buy - this might look like this:

Access 2010 exercise - Designing a database (image 3)

Note that in this case Quantity will be a text field

Apply referential integrity to your relationships:

Access 2010 exercise - Designing a database (image 4)

This is what the final diagram should look like

Close your database down when you have finished.

You can unzip this file to see the answers to this exercise, although please remember this is for your personal use only.
This page has 1 thread Add post
18 Mar 21 at 14:44

Should the name of the recipe or its id number be the key?

18 Mar 21 at 14:59

Life works better with databases if you create a numerical AutoNumber id column for every table, even if a perfectly good unique text field exists.  Access will work more quickly with an integer field, and it also gives you flexibility in using your database.  Trust me, we've been doing this for over 20 years!