• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Chapter 31. Upgrading Access 9x and 2000... > In the Real World—The Upgrade Blues

In the Real World—The Upgrade Blues

Every upgrade to Access (except the 1.0 to 1.1 transition) undoubtedly increased the market for mood-altering substances—both legal and illegal—among Access developers. Migrating from Access 97 to Access 2002 isn't a piece of cake. The larger and more complex your Access application, the more taxing the process. Access Basic detritus from Version 2.0 or earlier plagues the conversion of mature Access applications. (Many developers didn't upgrade Access 2.0 applications to Access 95 because of performance issues.) Thus, the more history behind your code, the greater the chance that it breaks when upgrading. Microsoft gains an immediate economic return on its investment in the transition to a common VBA 6.0 code base and editor for all Office applications; Access developers must settle for the deferred gratification of long-term standardization benefits.

The obvious temptation is not to upgrade any Access 9x application to Access 2002. This approach is viable only for applications you distribute as self-contained runtime versions generated by the Office 9x Developer Edition's Setup Wizard. Access 97 runtime versions install roughly 50MB of Access 97, Jet 3.51, DAO 3.51, and other obsolete dependency files on Office XP users'PCs. The Access 97 runtime baggage probably won't be a problem for today's desktop PCs, but road warriors'laptops usually have much less available disk space than desktops.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint