Microsoft Access 2010 Bible

Chapter 38: Upsizing Access Databases to SQL Server

1231

FIGURE 38.6

The final Access Upsizing Wizard dialog box

If, instead of upsizing all the Access tables to SQL Server, you had chosen Link SQL Server Tables

to Existing Application, the Upsizing Wizard would have modified your Access database to work

with the new SQL Server database. Queries, forms, reports, and data-access pages are automatically

linked to the data in the new Microsoft SQL Server database. The Upsizing Wizard renames the

tables to be upsized with the suffix _local and leaves them intact. For example, if you upsize a

table called Customers, the table is renamed Customers_local in your Access database. Then,

the Upsizing Wizard creates a linked SQL Server table named Customers.

Upsizing the entire Access application to an Access project connected to a SQL Server database

converts your application to a true client-server implementation. However, if you’ve been develop-

ing only Access databases until this point, you’ll find client-server development is quite different.

The Upsizing Wizard takes you only part of the way. The Upsizing Wizard doesn’t make any

changes to modules and macros. You might also need to make changes to your tables and queries

to reach full functionality in the new architecture.

Typically, the conversion process requires no more than a few minutes to complete, but the

elapsed time depends entirely on the size and complexity of the upsized Access database. A mes-

sage box displays the progress of the conversion, as shown in Figure 38.7.

Note
An error message will be displayed if the Upsizing Wizard encounters referential integrity errors during the
conversion process. You can click Yes to proceed with the conversion if you encounter an error message. Any
problem data is not converted to the new database. If you don’t want to omit the problem data, you must click
No to cancel the conversion process.