Share this Page URL

Chapter 22. Upsizing Jet Applications to... > Upsizing with the Trial-and-Error Ap... - Pg. 901

Upsizing Jet Applications to Access Data Projects 901 · Create a new project (.adp) file with a connection to the new SQL Database. · Copy all Jet forms, subforms, reports, subreports, pages, macros, and modules in the .mdb file to the new .adp file. The source files for Data access pages (DAP) must be local (not deployed on a Web server) in order for the Wizard to change the connection string in the .htm file. The Wizard makes no changes to VBA code behind forms or reports, or in modules. DAP that use relative connection strings, such as Northwind.mdb, won't upsize if you're running Windows XP Service Pack (SP) 1 Internet Explorer 6.0 SP1. Upsizing tables, queries, and Jet SQL statements is subject to the limitations described in sections later in this chapter. This chapter covers upsizing conventional single-file and front-end/back-end Jet applications. Chapter 24, "Designing and Deploying Data Access Pages," discusses issues with upsizing DAP to SQL Server data sources. Preparing to Upsize Your Jet Applications There are two basic approaches to increasing the probability of a fully successful upsizing operation: · Trial and error--Run the Wizard early and often to determine the scope of the additional effort necessary to upsize your Jet application successfully. If you have very large tables, you can use the structure-only option to minimize upsizing time. Read the Upsizing Wizard's report, make the changes necessary to upgrade missing objects, and try again. · Planned migration--Make changes to the Jet tables, queries, and application objects to mini- mize the likelihood of upsizing problems. For example, convert your VBA code that uses Data Access Objects (DAO) to ActiveX Data Objects (ADO) that use the OLE DB data provider for Jet. Thoroughly test your changes. If your Jet application is relatively simple or in the early development stage and doesn't include VBA