microsoft.com Home | |||
http://www.microsoft.com/office/ork |
After you convert a database from a previous version of Microsoft Access to Access 2000, you might need to make a copy of the database available for a user who is running Access 97. You can convert an Access 2000 database to an Access 97 database if it is not a member of a replica set. Any functionality that is specific to Access 2000 is lost when you convert the database to Access 97.
Converting an Access 2000 database to an Access 97 database makes the following changes to the converted database:
If the Access database is secure, remove user-level security. After you convert the database, you can secure the Access database in Access 97. If the Access database is protected with a password, you can convert the database without removing the password.
Important If the Visual Basic for Applications (VBA) code is protected with a password, you must supply the password before you convert the database. To supply the password, open a module to start Microsoft Visual Basic. On the Tools menu, click Database Name Properties, and then enter the password in the Password dialog box.
To convert an Access 2000 database to Access 97
If this is a multiuser database located on a server or in a shared folder, make sure that no one else has it open.
If you are converting a secured Access database, make sure that you have Open/Run and Open Exclusive permissions for the database and Read Design permissions for all objects in the database.
Note If your Access 2000 database contains code, you might need to fix missing references after you convert the database to Access 97. Also, if your Access database uses add-ins or library databases created in Access 2000, you must convert them back to Access 97.
You can convert code that uses Data Access Objects (DAO) back to Access 97, but you might receive a message that your computer is missing at least one of the Access 97 object libraries.
To fix the missing references in a converted database
Note Unlike Access 2000, Access 97 is not designed to work with ActiveX® Data Objects (ADO).
For more information about settings permissions in Access 2000, see Setting User-Level Security.
Topic Contents | Previous | Next | Top Friday, March 5, 1999 © 1999 Microsoft Corporation. All rights reserved. Terms of use. | ||
License
|