ACC: "Out of Memory" Opening V. 2.0 Database in V. 95/97

Last reviewed: May 30, 1997
Article ID: Q148445
The information in this article applies to:
  • Microsoft Access versions 7.0, 97

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

Advanced: Requires expert coding, interoperability, and multiuser skills.

When you open a Microsoft Access version 2.0 database using Microsoft Access 7.0 or Microsoft Access 97 for the first time, without converting the database to the new version, you may receive the following error messages:

   Out of Memory

   I/O Device Error

CAUSE

The Microsoft Jet database engine version 2.x ISAM is out of buffer space. This can occur when the Microsoft Access version 2.0 database contains many form modules and/or report modules.

RESOLUTION

Increase the number of buffers available to the Microsoft Jet database engine version 2.x ISAM by setting the MaxBufferSize parameter in the Windows Registry.

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows 95. 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 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 set the MaxBufferSize parameter in Microsoft Access 7.0, follow these steps:

  1. Start the Registry Editor and navigate to the following key:

    \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.0\Engines\Jet 2.x

  2. Using the right mouse button (right-click), click the "Jet 2.x" key, point to New, and then click Key.

  3. Type the following name for the new key:

    ISAM

  4. Right-click the "ISAM" key, point to New, and then click DWORD.

  5. Type the following name for the new DWORD:

    MaxBufferSize

  6. Right-click the "MaxBufferSize" DWORD, and then click Modify.

  7. In the Edit DWORD Value box, click the Decimal base option.

  8. In the Value Data box, enter 1024, and then click OK.

    NOTE: If your Microsoft Access version 2.0 database is very large, you may want to use a higher value such as 2048. The maximum value is 4096 using the Decimal base option (or 1000 Hexadecimal).

  9. Quit the Registry Editor.

  10. Start Microsoft Access 7.0 and open the Microsoft Access 2.0 database (without converting it). The database should open without error.

To set the MaxBufferSize parameter in Microsoft Access 97, follow these steps:

  1. Start the Registry Editor and navigate to the following key:

          \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Jet 2.x
    

  2. Using the right mouse button click the "MaxBufferSize" DWORD, and then click Modify.

  3. In the Edit DWORD Value box, click the Decimal base option.

  4. In the Value Data box, enter 1024, and then click OK.

    NOTE: If your Microsoft Access version 2.0 database is very large, you may want to use a higher value such as 2048. The maximum value is 4096 using the Decimal base option (or 1000 Hexadecimal).

  5. Quit the Registry Editor.

  6. Start Microsoft Access 97 and open the Microsoft Access 2.0 database (without converting it). The database should open without error.


Keywords : GnlOthr kbusage
Version : 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided


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: May 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.