ALL SOFTWARE EXERCISES
- EXERCISES HOME PAGE (862)
- Access 2010 (66)
- Access VBA Macros (17)
- Advanced VBA (29)
- ASP.NET MVC (0)
- ASP.NET webforms - C# (25)
- ASP.NET webforms - VB (27)
- Excel 2010 (83)
- Excel 2013 (10)
- Excel 2016 (0)
- Excel VBA Macros (37)
- Power BI - Excel 2013 (25)
- Power BI - Excel 2016 (23)
- Power BI Desktop (26)
- PowerPivot 2010 (26)
- Report Builder 3.0 (42)
- SQL (156)
- SSAS - multidimensional (21)
- SSAS - tabular (29)
- SSIS Integration Services (40)
- SSRS Reporting Services (53)
- Visual Basic 2010 (42)
- Visual C Sharp 2010 (65)
- WPF - Visual C# (20)
ACCESS 2010 EXERCISES
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.
The answer to the exercise will be included and explained if you attend one of more of the courses listed below!
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.