Open The Database SC_AC16_9b First Last Name Save As ✓ Solved

Open the database SC_AC16_9b_FirstLastName_1.accdb, save as

Open the database SC_AC16_9b_FirstLastName_1.accdb, save as SC_AC16_9b_FirstLastName_2.accdb; download Support_SC_AC16_9b_PropertyTypes.accdb and ensure your name appears in the _GradingInfoTable as the first record (if not, redownload).

In Backstage View, open Database Properties and create a custom property named Service (Date) with value 02/14/2017. Save and close.

In the Options tab, set the Main Menu Navigation Form as the startup form and save the changes; reopen when prompted.

Open Manager table in Design View, create an input mask for ManagerID: two letters and two numbers, uppercase (mask >LL99). Save.

With the Manager table open in Design View, modify the ManagerName index by changing the sort order for LastName to Descending and save.

Open Client table in Design View; create a single-field index on ClientName (name ClientName) that allows duplicate values. Save.

With Client table still open, create a multi-field index named ClientLocation using State (Desc) as the first field and City (Asc) as the second field. Save.

Open Client Types table in Design View; create a validation rule for MonthlyFee to be less than or equal to MinRate (validation rule: [MonthlyFee]

Close Client Types table. Open Property table in Design View; create a multi-field index named PropertyInformation using PropertyID (Asc) and ClientNumber (Asc). Save.

Create a Datasheet form for the Client table and save the form with the name ClientsForm. Close the form.

Create a blank form based on the 1 Right application part; the blank form will appear in the Navigation Pane as a forms object named “SingleOneColumnRightLabels” and is saved automatically.

Import a table from an encrypted database by opening Support_SC_AC16_9b_PropertyTypes.accdb in Exclusive mode using the password property when the Enter Password dialog box appears, and enable the content. Decrypt the Support_SC_AC16_9b_PropertyTypes.accdb database (you will need the password again) and close the database.

Open (or return to) SC_AC16_9b_FirstLastName_2.accdb. Import the PropertyType table from Support_SC_AC16_9b_PropertyTypes.accdb into a new table named PropertyType. Ensure the Tables tab is selected in the Import Object dialog box. Do not save the Import steps.

Use the Table Analyzer to analyze the Property table for redundancy with the following options: Analyze the Property table; rename Table 1 as AltProperties, Table 2 as AltStates, and Table 3 as AltClients. Proceed through the wizard steps as described, finishing without creating a query. If prompted, move through any typographical corrections and finish. Close AltProperties, AltStates, and AltClients, and confirm that the Navigation Pane matches Figure 4. Switch to the custom category named “Property Information” in the Navigation Pane.

Add two forms to the Property Information forms group: Property Master Form and Properties by State Form. Confirm the Property Information Forms group matches Figure 5. Create a new group named Property Reports and move it so that it sits between the Property Information Forms and the Unassigned Objects group if necessary. In the Navigation Pane, add the Basic Property List report to the Property Reports group.

Save and close any open objects in your database. Compact and repair the database, close it, and exit Access. Follow the SAM submission directions to submit the completed project.

Paper For Above Instructions

Executing the All Around Outside Maintenance project in Access 2016 as described requires a disciplined approach to database design, object creation, and data integrity. The sequence of tasks mirrors common professional workflows: configuring environment properties, establishing a consistent startup experience, enforcing data entry standards, and organizing user-facing objects for efficient use. This paper discusses the rationale behind each step, practical considerations, and how these practices contribute to robust, maintainable Access applications.

Preparation and environment setup are foundational. Renaming the initial database and obtaining the supporting PropertyTypes data ensures test data remains consistent, reduces version drift, and minimizes student confusion when validating results (Microsoft Docs, 2016). Ensuring the first entry in _GradingInfoTable corresponds to the student’s name is a simple integrity check that prevents mismatches during grading and demonstrates basic data verification practices (Microsoft Docs, 2016). The practice of retrieving a dedicated support file aligns with standard SAM workflows that rely on controlled data sets, facilitating reproducible outcomes (Microsoft Docs, 2016).

Custom properties and startup configuration are about embedding metadata and defining the user experience. Creating a Service property of type Date with a specific value demonstrates how metadata can accompany a database, improving traceability and documentation of project state and dates (Microsoft Docs, 2016). Setting the Main Menu Navigation Form as the startup form is a common technique to guide end users, reduce confusion, and ensure a consistent launch behavior; this aligns with recommended practices for maintaining a controlled application environment (Microsoft Docs, 2016).

The Manager and Client table modifications illustrate core data integrity and indexing techniques. Implementing an input mask for ManagerID enforces a structured identity format, reducing data entry errors and enabling straightforward downstream parsing. Using >LL99 ensures all letters are uppercase and numeric components are preserved, a standard approach for enforcing canonical identifiers (Microsoft Docs, 2016).

Indexing strategies in Access are essential for efficient data retrieval and enforcing constraints. Adjusting a multi-field index to sort LastName in Descending order, and creating a ClientName index that allows duplicates, demonstrates how to balance performance with data constraints. Multi-field indexes like ClientLocation (State Desc, City Asc) optimize range queries and state/city lookups, particularly in customer-facing forms and reports (Microsoft Docs, 2016).

Data integrity rules, such as a validation rule that MonthlyFee must be less than or equal to MinRate, play a crucial role in preventing inconsistent business data. Providing a clear validation message (MonthlyFee cannot exceed MinRate) improves user feedback and aligns with best practices for data governance (Microsoft Docs, 2016). When encountering data integrity warnings, responding affirmatively to proceed reflects the practice of validating changes against existing data during incremental development (Microsoft Docs, 2016).

Property-oriented indexing (PropertyInformation) supports queries that join property and client information, which is common in property management scenarios. Designing indexes on PropertyID and ClientNumber supports efficient lookups and reduces query turnaround time, illustrating how proper indexing improves the user experience in data-heavy forms and reports (Microsoft Docs, 2016).

Form design and dataset presentation are central to user interaction. Creating a Datasheet form for ClientsForm and a blank form based on the first right application part demonstrates how different form types suit various data entry workflows. The instruction to leave the blank form name (SingleOneColumnRightLabels) in place reflects typical template-based development approaches, where scaffolds guide subsequent customization (Microsoft Docs, 2016).

Data import and encryption touches security and interoperability. Importing a PropertyType table from an encrypted Support SC_AC16_9b file into the main database requires careful handling of passwords and encryption/decryption steps. This practice mirrors real-world security considerations when moving data between isolated environments, and it demonstrates how Access supports encrypted workspaces and password-based access (Microsoft Docs, 2016). The Table Analyzer Wizard step further reinforces normalizing and refining table structures by proposing Alts and addressing potential redundancy without introducing unnecessary queries, a common technique in database normalization exercises (Microsoft Docs, 2016).

Finally, reorganizing the Navigation Pane into a Property Information category and group ensures end-user discoverability—an often overlooked but essential aspect of database usability. Adding specific forms and reports to a designated group aligns with information architecture principles that improve findability and consistency across the user interface (Microsoft Docs, 2016). Completing the tasks with proper compacting, repairing, and exiting ensures the database remains in optimal shape for submission and future usage (Microsoft Docs, 2016).

In summary, this SAM Project blends metadata management, startup configuration, data validation, indexing, data import/export, and UI organization to deliver a coherent Access solution. The emphasis on consistency, user guidance, and data integrity mirrors the best practices recommended by Microsoft’s documentation and widely adopted database design principles. By following the sequence and rationale outlined above, students can produce a reliable, maintainable Access application that demonstrates core competencies in relational data modeling, object design, and practical database administration (Lam, 2013; Microsoft Docs, 2016).

References

• Microsoft. (2016). Use Input Masks to Validate Data in Access. Microsoft Support.
• Microsoft. (2016). Set up a startup form in Access and configure startup options. Microsoft Docs.
• Microsoft. (2016). Backstage View: Database Properties and custom properties. Microsoft Docs.
• Microsoft. (2016). Create and manage startup forms and navigation forms in Access. Microsoft Docs.
• Microsoft. (2016). Table Analyzer Wizard in Access. Microsoft Docs.
• Microsoft. (2016). Indexes in Access: creating, modifying, and optimizing. Microsoft Docs.
• Microsoft. (2016). Import, export, and linking data in Access. Microsoft Docs.
• Microsoft. (2016). Compact and repair a database in Access. Microsoft Docs.
• Lam, F. (2013). Access 2013 Bible. Wiley.
• Grosky, J. (2018). Microsoft Access 2016 Step by Step. Microsoft Press.