- Access exercises (91)
- C# exercises (79)
- Excel exercises (278)
- Power Apps exercises (13)
- Power Automate exercises (18)
- Power BI exercises (139)
- Power Platform exercises ()
- Python exercises (28)
- Report Builder exercises (141)
- SQL exercises (198)
- SSAS exercises (51)
- SSIS exercises (46)
- SSRS exercises (99)
- VBA exercises (85)
- Visual Basic exercises (46)
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.
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:
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:
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:
Note that in this case Quantity will be a text field
Apply referential integrity to your relationships:
This is what the final diagram should look like
Close your database down when you have finished.
Should the name of the recipe or its id number be the key?
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!