Protect databases - Microsoft Access 2013 - page 343

In this exercise, you'll first back up a database. Then you'll run the Compact And Repair
Database, Analyze Performance, and Database Documenter utilities.

SET UP You need the GardenCompany12 database you worked with in the preceding
exercise to complete this exercise. Open the database file FOR EXCLUSIVE USE, and then
follow the steps.

1

Close any open database objects, and then display the Save As page of the
Backstage view.

2

In the Advanced area of the right pane, double-click Back Up Database .

3

In the Save As dialog box, verify that the contents of the Chapter12 practice file
folder are displayed, and then click Save , which creates a copy of the database with
the current date appended to the file name in the specified folder.

TIP As with any file name, you can change the name to suit your needs.

Now let's run the Compact And Repair Database utility.

4

Display the Info page of the Backstage view, and then click Compact & Repair
Database .

TIP You can also click the Compact And Repair Database button in the Tools group
on the Database Tools tab.

TROUBLESHOOTING If you don't have enough space on your hard disk to store a tem-
porary copy of the database, you don't have appropriate permissions, or another user
also has the database open, the Compact And Repair Database utility will not run.

The utility takes only a few seconds to run, and the database will not look any dif-
ferent. If you have been using a database regularly and have not compacted it for a
while, running the Compact And Repair Database utility can sometimes reduce the
file size by as much as 25 percent.
Next let's run the Analyze Performance utility.

12

5

Close any open database objects, and then in the Forms area of the Navigation
pane, click Home Page .

6

On the Database Tools tab, in the Analyze group, click the Analyze Performance
button to open the Performance Analyzer dialog box. Notice that each type of data-
base object is represented by a page, and there are also pages for all objects and for
the database as a whole.