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

Troubleshooting

Compile Errors in the Convert Database Process

Q1:Error messages appear when converting to Access 200x from early Access versions.
A1: Access 2.0 and earlier were 16-bit applications. The first error message you might receive is “There are calls to 16-bit dynamic-link libraries (.dll) in this application.” In this case, you must alter the code of Declare statements to call the current 32-bit equivalents of the 16-bit DLLs. For example, you must change calls to functions in User.dll, Kernel.dll, and Gdi.dll to User32.dll, Kernel32.dll, and Gdi32.dll.

A more common error message when converting Access 2.0, 95, and 97 applications is “There were compilation errors during the enabling or conversion of this database.” If you're converting from Access 2.0, many of these errors are likely to arise from Access Basic reserved words and symbol usage that VBA 6.0 doesn't support. Similar problems occur with applications that originated in Access 2.0 or earlier and were converted to Access 9x. In some cases, conversion of earlier application versions to Access 97 and then to Access 2000 is easier than attempting direct conversion. There's seldom a need to convert Access 97 and earlier files to Access 2002. See Chapter 31 for additional information on conversion issues.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


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