Microsoft Knowledge Base Email Alertz

When you link a Microsoft Access 2.0 table to a Microsoft Access 2000 database, you may receive the following error message: Cannot open a database created with a previous version of your application. Cannot open a database created with a

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 208419 - Last Review: July 14, 2004 - Revision: 1.2

ACC2000: Error Message When You Link Access 2.0 Tables

This article was previously published under Q208419
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/EN-US/ ) Description of the Microsoft Windows Registry
Advanced: Requires expert coding, interoperability, and multiuser skills.

This article applies only to a Microsoft Access database (.mdb).

SYMPTOMS

When you link a Microsoft Access 2.0 table to a Microsoft Access 2000 database, you may receive the following error message:
Cannot open a database created with a previous version of your application.
Similarly, you may receive this error message when you use Microsoft Visual Basic for Applications to link an Access 2.0 table or if you open a program in Visual Basic for Applications that contains a link to an Access 2.0 table.

This error message may also occur if you try to convert a database from an earlier version of Access.

CAUSE

This behavior can occur when the Microsoft Jet database engine version 2.x key (Jet 2.x) is missing from the Microsoft Windows registry in the following location:
HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\ISAM Formats

RESOLUTION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To restore the correct registry settings, follow these steps:
  1. Open the Windows Registry Editor (Regedit.exe).
  2. Navigate to the following registry key:
    HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\ISAM Formats
  3. Right-click ISAM Formats, point to New, and then click Key.
  4. Rename the newly created key to Jet 2.x
  5. Click to open the Jet 2.x key and insert the following values in the right pane of the Registry Editor:
        Name                Type          Data
        ------------------------------------------
        CreateDBOnExport    REG_BINARY    00
        Engine              REG_SZ        Jet 2.x
        IndexDialog         REG_BINARY    00
        IsamType            REG_DWORD     0x00000000 (0)
        OneTablePerFile     REG_BINARY    00
    					
  6. Close the Registry Editor.
  7. Start Access and link the Access 2.0 tables.

MORE INFORMATION

The Jet 2.x key may be missing because of the removal of a run-time program created with the Microsoft Office 2000 Developer Edition Tools.

REFERENCES

For more information about linking data, click Microsoft Access Help on the Help menu, type link tables in the Office Assistant or the Answer Wizard, and then click Search to view the topics returned.

APPLIES TO
  • Microsoft Access 2000 Standard Edition
Keywords: 
kberrmsg kbenv kbprb KB208419
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate