Exp19_Access_Ch09_Cap – Trading Cards 1.0

Exp19_Access_Ch09_Cap – Trading Cards 1.0

 #Exp19_Access_Ch09_Cap – Trading Cards 1.0

Exp19 Access Ch09 Cap – Trading Cards 1.0

Project Description:

You and your partner Stann Dupp have a small business selling  baseball cards online through eBay. As the more computer-savvy partner;  you created an Access database with records of the cards you have in  stock. As it turns out, Stann was attempting to manage the card  inventory and ended up modifying crucial aspects of the database that  impact the general operation of the database. You will reverse those  changes and create other safeguards to protect from this happening again  in the future. The database tables may already be normalized; however,  you will examine the tables to verify.

Start Access. Open the downloaded   Access database named Exp19_Access_Ch09_Cap_Trading_Cards.accdb.  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.

You   will first establish relationships between the Cards, Brands,  and Rarity   tables based on the common fields that they share.
 

  Open the Relationships window. Add the Cards,   Brands, and Rarity tables to the layout.

After   creating a relationship between two tables, you will enforce  referential   integrity, which ensures that the relationship will remain  intact if/when   data is updated in either table. Furthermore, you will  ensure that all   changes to the primary key in your Cards table will  be reflected in the foreign   keys that exist in the Rarity table by  selecting the Cascade Update Related   Fields option.
 

  Create a relationship between the Cards   and Rarity tables tables, ensuring   you check the Enforce Referential   Integrity and Cascade Update   Related Fields options for the relationship.

After   also establishing the relationship between the Cards and  Brands tables, in   the same manner, you will analyze the database to  identify any flaws in the   design as well as suggested low-risk  improvements that can be made to your   database.
 

  Create a relationship between the Cards   and Brands tables, ensuring you   check the Enforce Referential   Integrity and Cascade Update   Related Fields options for the relationship. Save, and close the   Relationships window. Open the Performance   Analyzer dialog box, under All Object Types, click Select All, and then click OK.   Note the idea to relate the Cards table to the others in the database. Close   the Performance Analyzer.

You   will now provide your users with a simple and intuitive way to add and edit   cards by creating a form.
 

  Create a new form based on the Cards   table using the Form tool. Save   the form as Add or Edit Cards.   Close the form.

Now   that you have the Add or Edit Cards form created, you can add  that and the   remaining forms to a Horizontal Tab navigation form. By  doing this, you will   create a one-stop-shop for your users to view and  edit the trading cards in   the database.
 

  Create a navigation form based on the Horizontal   Tabs template. Drag the Add or   Edit Cards form to the first tab position.

Drag   the All Player Cards report to the   second tab position.

Drag   the Bowman Cards report to the   third tab position.

Drag   the Donruss Cards report to the   fourth tab position.

Drag   the Fleer Cards report to the   fifth tab position.

Drag   the Topps Cards report to the   sixth tab position.

Switch   to Form view and test the navigation form. Save the navigation form with the   default name and close it.

You   will finalize the interface for your users by hiding the  Navigation Pane so   that it is out of their way, and setting the  navigation form you created to   open automatically when the database  opens. This ensures that the user’s   experience is seamless and  straightforward.
 

  Set the database to hide the Navigation Pane and open the  navigation form   when the database opens. Close the database and reopen  it observe that the   form opens automatically.

Close   all database objects. Close the database and then exit Access. Submit the   database as directed.