You have cataloged your vintage video games in an Access database. In this project, you add two tables to a database you have started? One to identify the game system

You have cataloged your vintage video games in an Access database. In  this project, you add two tables to a database you have started? One to  identify the game system that runs your game and the other to identify  the category or genre of the game. Then you will join each table in a  relationship so that you can query the database. Start Access. Open the downloaded   Access file named .  Grader has automatically added   your last name to the beginning of the  filename. Save the file to the   location where you are storing your  files. Open   the Games table and review the fields containing the game information. Close   the table. Create a new table in Design view. Add the field name and select as the Data Type. Add the caption . Set the SystemID field as the primary   key for the table. Add   a second field named with the .   Change the SystemName field size property to .   Add the caption .   Save the table as . Switch   to Datasheet view and enter the following system names, letting Access assign   the System ID: Double-click the to the   right of the System Name column to set the column width to Best Fit. Save and   close the table. Create   a new table in Design view. Add the field name and select as the Data   Type. Add the caption .   Set the as the   Primary Key for the table. Add   a second field named and accept as the Data   Type. Change the field size property to .   Add the caption .   Save the table as . Switch   to Datasheet view, and enter the following Category Description, letting   Access assign the Category ID: Close the table. Establish   relationships in the database by adding the , and tables to the Relationships   window. Close the Show Table dialog box.  Create a one-to-many relationship   between the SystemID field in the  System table and the SystemID field in the   Games table, enforcing  Referential Integrity. Select the option to cascade   update the related  fields. Create   a one-to-many relationship between the CategoryID field in  the Category table   and the CategoryID field in the Games table,  enforcing Referential Integrity.   Select the option to cascade update  the related fields. Save and close the   Relationships window. Create   a simple query using the Query Wizard. From the Games table, add the and fields (in that order). Save the query using the title . Switch to Design view. Sort the   Rating field in ascending order. Click   the at the   top of the Rating field, then click and drag the to move it to the first position of the query design grid.   Add a Total row, click in the of the GameName column, click the ,   and then select .  The records   will be grouped by rating, and the number of games will  be counted for each   group. Run, save, and close the query. Create   a new query in Design view. Add the , , and tables to the query design window. Add the following   fields to the query (in this order). Sort   the query in ascending order by GameName and run the query. Save the query as and close the query. Copy   the in the   Navigation pane and paste it with the name .   Modify the query in Design view by using as the criteria for SystemName. Remove the sort by GameName and sort  in   ascending order by CategoryDescription. Save and run the query.  Close the query. Create   a new query in Design view. Add the and tables to   the query design window. Add fields (in this order) to  display the name of   the game, its rating, the category description of  the game, and the system   name. You only want to display Wii games with  a rating of or .    Because the system name is the same for the games you plan to pack and  share,   hide this value from the results. Save the query as and run the query. Close the query.

Do you need us to help you on this or any other assignment?


Make an Order Now
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *