ACC95: "Unrecognized database format" Using Database Documentor

Last reviewed: October 20, 1997
Article ID: Q175380
The information in this article applies to:
  • Microsoft Access 7.0

IMPORTANT: This article contains information about editing the registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.

SYMPTOMS

When you try to run the Database Documentor on an object in a Microsoft Access 7.0 database, you may receive the following error message:

   Unrecognized database format
   '<Path to Temp File>'

When you click OK, the Database Documentor does not run.

CAUSE

The MaxBufferSize setting in the Jet\3.0\Engines\Jet folder in the Windows Registry is too low. For example, this problem may occur after you have installed Microsoft Team Manager 97.

RESOLUTION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the Changing Keys And Values online Help topic in Registry Editor (Regedit.exe). Note that you should make a backup copy of the registry files (System.dat and User.dat) before you edit the registry.

To modify the MaxBufferSize setting, follow these steps:

  1. On the Windows 95 taskbar, click Start, and then click Run.

  2. In the Run dialog box, type "regedit" (without the quotation marks) in the Open box.

  3. Locate the following registry key:

          HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\3.0\Engines\Jet
    

  4. Select MaxBufferSize, and on the Edit menu, click Modify.

  5. In the Edit DWORD Value dialog box, enter 0 in the Value data box, and then click OK.

NOTE: You can also delete the MaxBufferSize entry. To delete the entry, select MaxBufferSize, and then on the Edit menu, click Delete. Deleting the entry or setting it to 0 will not affect the performance of other programs. In this case, Microsoft Jet 3.0 calculates the default buffer size for the computer, and this value is never below 512.

MORE INFORMATION

Steps to Reproduce Behavior

  1. On a computer running Microsoft Access 7.0, click Start on the Windows 95 taskbar, and then click Run.

  2. In the Run dialog box, type "regedit" (without the quotation marks) in the Open box.

  3. Locate the following registry key:

          HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\3.0\Engines\Jet
    

  4. Select MaxBufferSize, and then on the Edit menu, click Modify.

  5. In the Edit DWORD Value dialog box, click Decimal and enter 128 in the Value data box; then click OK.

  6. Start Microsoft Access 7.0.

  7. Open the sample database Northwind.mdb.

  8. On the Tools menu, point to Analyze, and then click Documentor.

  9. Choose any database object and click OK. Note that you receive the error message described in the "Symptoms" section.

REFERENCES

For more information about how Microsoft Team Manager 97 affects the MaxBufferSize setting in the system registry, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q165041
   TITLE     : TMGR: Max Buffer Size Set Too Low

For more information about backing up the system registry, please see the following article in the Microsoft Knowledge Base:

   ARTICLE-ID: Q135120
   TITLE     : Configuration Backup Tool for Backing Up the Registry

For more information about Windows Registry settings for Microsoft Jet 3.0, search the Microsoft Access 7.0 Help Index for "Jet database engine, Registry settings" and display the topic "Initializing the Microsoft Jet 3.0 Database Engine."


Additional query words: prb wizard documenter
Keywords : GnlDbdoc kberrmsg
Version : WINDOWS:7.0
Platform : WINDOWS
Hardware : x86
Issue type : kbprb
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.