Illustrated Access 365 | Module 2: SAM Project B скачать в хорошем качестве

Illustrated Access 365 | Module 2: SAM Project B

Please contact us if you need this project or any other project in any subject to be completed. Whatsapp: +1-343-321-3276 Email: [email protected] #illustratedaccess365 #MediterraneanTours Illustrated Access 365 | Module 2: SAM Project B Mediterranean Tours IMPORTING TABLES AND MODIFYING TABLES AND TABLE PROPERTIES PROJECT STEPS 1. Most of the data that you need for the Mediterranean Tours database is currently stored in Excel workbooks. Use the Import Spreadsheet Wizard to import the data from the Support_AC365_2B_CruiseLines.xlsx support file and append it to the CruiseLines table. Do not analyze the table after importing the data and do not save the import steps. Open the CruiseLines table in Datasheet View. It should look like Figure 1. Close the CruiseLines table. 2. Tour guides manage groups of cruise passengers when they disembark and go on various shore excursions, and some tour guides offer additional services. Use the Import Spreadsheet Wizard to import the data from the Support_AC365_2B_Services.xlsx support file as a new table. The first row contains a column heading, but no other change needs to be made to the field. Let Access add a primary key to the table. Name the table Service and do not save the import steps. Open the Service table in Datasheet View. It should look like Figure 2. Close the Service table. 3. Open the TourGuide table in Design View. TourGuides can reside in any region, but most TourGuides reside in the Italy region. Change the Default Value property for the Residence field to IT. Save the change but do not close the table. 4. With the TourGuide table open in Design View, change the Input Mask property for the StartDate field to Medium Date. Save the change and close the table. 5. Open the CruiseLines table in Design View. Change the Required property for the CruiseLineName field to Yes. Save the change to the CruiseLines table and then close the table. (Hint: Because you changed the Required property, the "Data Integrity rules have been changed" warning message appears. The data is valid, so click No, and continue saving the table.) 6. Open the TourGuide table in Datasheet View. Apply the Currency format to the Salary field. Save the change but do not close the table. 7. With the TourGuide table still open in Datasheet View, move the Salary field so that it appears immediately after the StartDate field. Save the change and close the table. 8. Open the Service table in Datasheet View and make the following changes: a. Resize the Description field so that all field values are completely visible. b. Add a new field following the Description field with the field name Rating and the Number data type. Save the changes and close the table. 9. Open the TourGuide table in Datasheet View. Delete the Mobile field and save the change. 10. With the TourGuide table still open in Datasheet View, decrease the number of decimal places for the Salary field to 0. Save the change and close the table. 11. Open the Service table in Design View and make the following changes to the Rating field: a. Change the default value to 4. b. Increase the number of decimal places to 2. Save the changes and close the table. 12. In the Navigation Pane, rename the Region table, using MedRegion as the name. 13. Open the Service table in Design View and add a new field below the Rating field named TourGuideID with a Number data type. This field will serve as the foreign key field to allow one record in the TourGuide table to link to many records in the Service table. Save and close the Service table. 14. Open the Relationships window, add the Service table and the TourGuide table, and create a one-to-many relationship between the TourGuide and Service tables using the common TourGuideID field. Enforce referential integrity on the relationship. 15. With the Relationships window still open, add the Speciality table, and create a one-to-many relationship between the Speciality table and TourGuide table using the common SpecialtyCode field. Enforce referential integrity on the relationship. The Relationships window should look like Figure 3. Save and close the Relationships window.