A.6. Enabling a Database

As mentioned at the beginning of this appendix, Access 2003 can open databases in prior versions of Access by either enabling or converting the database. If the database created in Access 97 or earlier is opened by Access 2003, the Convert/Open Database window will appear, see Figure A-3. This window clearly states the effects of each option. The Convert/Open Database dialog box appears each time an earlier version database is opened. So, if down the road, converting becomes the desired avenue, it is only a click away.

Enabling allows a user with Access 2003 to open a database created in an earlier version of Access without converting the file to the Access 2003 file format. The 2003 user will be able to add, delete, and modify records and to view database objects, but they will not be able to modify database objects or add new objects. Enabling is quite beneficial if there are users who have still not upgraded to Access 2003. It allows the same application file to be shared by multiple versions of Access.

There are some logical limitations when working with an enabled database. Considering that databases are not forward compatible, it makes sense that you cannot link or import an Access 2003 table to an enabled database. (Obviously the enabled database is in an earlier format or it wouldn't need to be enabled.) However, you can open a 2003 database and export the tables to a prior-version database. You can also move or copy data from a 2003 table and paste it directly into a table in a prior-version database.

For ease and consistency, when a database is enabled in 2003, the custom toolbars and menu bars are temporarily converted to the new style of menu and toolbars. In this case, "temporarily" means that the conversion is not preserved when the file is closed. And, although menu bar macros are not converted, they are still supported. So, although they can be used, they cannot be modified.

Yet again, security requires special treatment, or at least special acknowledgment. When a database with user-level security is enabled in 2003, it is recommended that the WIF is recreated in 2003. This ensures that proper security is retained. However, if recreating the WIF (MDW file) is not practical, then it will be necessary to join the original WIF in order to sign into the database.