About converting or enabling a secured database from a previous version of Microsoft Access

Using a secured database from a previous version of Microsoft Access requires some additional steps and considerations.

Important   To convert or enable a secured database, you must meet the following requirements or conversion will fail:

• When you install Microsoft Access 2000, it creates a new workgroup information file and makes it the current file. Therefore, before you convert a secured database, you must join the workgroup information file that defines the user accounts that are used to access the database you wish to convert, or that were in use when the database was secured. For information on joining a workgroup information file, click .
  
  
• The user account you use to log on during conversion must have the following permissions:

  Open/Run and Open Exclusive permissions for the database itself.

  Modify Design or Administer permissions for all tables in the database, or you must be the owner of all tables in the database.

  Read Design permissions for all objects in the database.

If all users of a previous-version secured database will be upgrading to Microsoft Access 2000, you should convert the database and workgroup information file used with it. How you proceed depends on which version of Microsoft Access you are upgrading from.

If only some users of a secured database will be upgrading to Microsoft Access 2000, you can share the database and workgroup information file across all versions of Microsoft Access currently in use. There are several ways to share the secured database and workgroup information file.

Important   Only convert a previous-version secured database if all users of the database are upgrading to Microsoft Access 2000. If only some users are upgrading, you can share the database in its current format.

Important   Because you cannot protect Microsoft Visual Basic code in modules and code behind forms and reports with user-level security in Microsoft Access 2000, code converted from a secure database of a previous version is no longer secure. Learn about protecting Visual Basic code.