Article ID: 141296
Article Last Modified on 1/19/2007
APPLIES TO
- Microsoft Access 95 Standard Edition
- Microsoft Access 97 Standard Edition
This article was previously published under Q141296
Moderate: Requires basic macro, coding, and interoperability skills.
This article applies only to a Microsoft Access database (.mdb).
SUMMARY
When you convert a Microsoft Access version 1.x or 2.0 database to a
Microsoft Access 7.0 or Microsoft Access 97 database, the conversion
process may display a warning message or stop altogether because of an
incompatibility with new features and enhancements. This article discusses
general troubleshooting tips for the unusual case when Microsoft Access
cannot convert a database successfully.
REFERENCES
For additional information about Access 97 conversion issues, click the article number below
to view the article in the Microsoft Knowledge Base:
160949 ACC97: Where to Find Conversion Information for MS Access 97
For additional information about converting databases that use 16-bit application programming interface (API) calls, click the article number below
to view the article in the Microsoft Knowledge Base:
Q147781 ACC: How to Convert API Calls from 16-bit to 32-bit.
For more information about database conversion and compatibility, click
Contents and Index on the
Help menu, click the
Index tab in Access Help, type the following text
conversion and compatibility
and then double-click the selected text to go to the
"Conversion and Compatibility Issues" topic. If you are unable to find the information you need, ask the Office Assistant.
For information about issues related to converting a database, read the
"Conversion and Compatibility" section of the Acread80.wri file in your
Microsoft Access 97 folder (or in the Acreadme.txt file in your Microsoft
Access 7.0 folder.)
Additional query words: inf
Keywords: kbhowto kbusage KB141296