Chapter 38: Upsizing Access Databases to SQL Server
1233
FIGURE 38.8
The Upsizing Wizard reportTip
The report snapshot is stored in the same folder as your application so that you can refer to it later.
The Upsizing Wizard Report is a good place to start when verifying the upsize process. The report
tells you which Access database objects must be manually re-created in SQL Server and which
tasks could not be completed by the wizard. A typical example of conversion failure is an Access
query that contains a reference to a custom VBA procedure. There is no way for the Upsizing
Wizard to recreate VBA logic in a SQL Server database, so you’ll have to prepare a workaround
after the upsizing task is complete.Working with an Access ADP file
After you’re finished reviewing the report, close it. When you close the report, the Upsizing
Wizard automatically loads the new Access project. The Access Upsizing Wizard migrates the
native Access objects into their corresponding objects in the new Access project. Although Access
projects are organized into the same object groupings (tables, queries, forms, reports, and so on),
ADP objects differ significantly in how they work compared to native Access. Here are the charac-
teristics of ADP objects and how they differ from the Access objects you work with in an .accdb
database: