A newly created Access 97 database is not secure when you convert a security-enhanced Access 2000 database to Access 97 format
Article ID: 198986
Article Last Modified on 1/23/2007
APPLIES TO
- Microsoft Access 2000 Standard Edition
- Microsoft Access 97 Standard Edition
This article was previously published under Q198986
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
SYMPTOMS
When you convert a security-enhanced Microsoft Access 2000 database to Microsoft Access 97 format, the newly created Access 97 database is not secure. Permissions are reset to their defaults in the newly created Access 97 database. This problem occurs because Access 2000 uses a new workgroup file that cannot be read by Access 97. Therefore, permissions on objects in the new database are reset.
Note The permissions on the source Access 2000 database are not affected. This problem does not constitute a security breach. When you convert a security-enhanced Microsoft Access 2000 database to Microsoft Access 97 format by using "Save As", you must have read-design permissions on all objects. Also, you must know the Microsoft Visual Basic for Applications project password, if one exists, to perform the conversion. If you have read-design permissions on all objects and you know the Visual Basic for Applications project password in Access 2000, you already have permissions to view the design of the objects.
RESOLUTION
If you want to have a security-enhanced version of the Access 97 database, the database administrator must re-secure the database in Access 97.
Additional query words: prb ACC2000
Keywords: kbtshoot kbprb KB198986