BUG: Compacted 1.1 DB Becomes 2.0 DB w/ Compatibility Layer (115779)
The information in this article applies to:
- Microsoft Visual Basic Standard Edition for Windows 3.0
- Microsoft Visual Basic Professional Edition for Windows 3.0
- Microsoft Access 2.0
This article was previously published under Q115779 SYMPTOMS
Error 3041 "Incompatible database version" is the result when you use
the Microsoft Access 2.0/Visual Basic 3.0 Compatibility Layer to open
a Microsoft Access version 1.1 database that was compacted by using the
CompactDatabase statement with the DB_VERSION10 option.
CAUSE
According to the README.TXT file for the Compatibility Layer, after
installing the Compatibility Layer, the CompactDatabase statement in Visual
Basic version 3.0, when used with the DB_VERSION10 constant (from the file
DATACONS.TXT), is supposed to generate a Microsoft Access version 1.1
database. The following table shows which type of database is supposed to
be created when you use CompactDatabase with and without DB_VERSION10:
------------------------------------------------------------------
Jet Database Engine Creates by Default With DB_VERSION10
------------------------------------------------------------------
Version 1.1 Version 1.1 database Version 1.0 database
Version 2.0 Version 2.0 database Version 1.1 database
However, this is not what happens. There is a bug in the Compatibility
Layer that causes the CompactDatabase statement to always create a
Microsoft Access version 2.0 database regardless of the existence of the
constant DB_VERSION10 as an option. Both the Office Development Kit (ODK)
and Access Developer's Toolkit (ADT) versions of the Compatibility Layer
have this problem.
WORKAROUND
Use Microsoft Access version 1.1 or 2.0 to compact a version 1.1
database instead of using the CompactDatabase statement from the
Compatibility Layer.
NOTE: Once a database is in Microsoft Access version 2.0 format, you
cannot convert it back to Microsoft Access version 1.1 format directly.
If you used CompactDatabase and ended up turning a version 1.1 database
into a version 2.0 database, you need to restore the version 1.1 database
from a backup copy, or rebuild it by extracting the information from
the newly compacted version 2.0 database and placing it into a new
version 1.1 database.
WARNING: If the Compatibility Layer has been installed and you're using
a Microsoft Access version 1.1 database with a Visual Basic application,
NEVER use CompactDatabase on the version 1.1 database if you want it to
remain in version 1.1 format. Instead, use Microsoft Access itself to
compact version 1.1 databases.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. We are researching this problem and will
post new information here in the Microsoft Knowledge Base as it becomes
available.
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | kbbug KB115779 |
---|
|