Considerations for converting Legacy databases to ACCESS2000

As the ACCESS97 (or earlier version) can not open ACCESS2000 production of files, so as the previous revision, to fully play the function of ACCESS2000, readers must consider the old version of the database conversion to 2000, see the following instructions:

First, the Common data table

Regardless of the version of the database, the data table is a shared resource, such as the ACCESS97 database can be linked to the data table from the ACCESS2000 database, so if not every user in the environment has been upgraded to ACCESS2000, and to maintain the correct data, the data table can be used as a common.

Second, ACCESS2000 conversion to ACCESS97

This is the first time in access to the revision of the new version of the function, the reader can open the database, using Tools 〗->〖 Database Tools 〗->〖 Conversion database 〗->〖 conversion ACCESS97 file format. However, the converted database does not guarantee that everything is OK in the ACCESS97, because if the database uses a new feature that is not supported in version 97 in 2000, an error will occur after the conversion.

Third, unsupported program library

If the reader converts a ACCESS7.0 database and uses DAO to process the database in VBA, an error occurs during conversion because ACCESS2000 does not support the dao2.5/3.x library.

The workaround is to start the Visual Basic programmer after the conversion, using tool 〗->〖 to set the reference item option, clearing the missing dao2.5/3.x library, and referencing the DAO3.60 library.

Four, the program code

In the Code section, if you convert a ACCESS2.0 database and use API functions in a Declare statement in the database, all such functions must be declared again after conversion, still using the Declare statement, but each function has a new syntax. Because Access2.0 is using the WIN16 API, the current person is the WIN32 API.

In addition, in ACCESS2000 VBA, some properties and functions return values have a more stringent classification, usually the old version of the return value type to the variant is converted to a string, it is possible to execute errors, the reader can be completed after the conversion, open the Visual Basic programmer, Use the debug 〗->〖 compile option here to see if there are errors, the most common error is type mismatch or incorrect use of 〖null, and so on, you can check that the property or function that you are handling returns the correct value.

Description

The above list only the more common or possible errors, generally speaking, ACCESS2000 and ACCESS97 difference is not large, the conversion of 97 to 2000 should not be too much problem, The problem is more ACCESS2.0 and version 7.0, because these two versions are not 32-bit version, plus Access2.0 does not support VBA, so there are more problems.