ACC95: "Not Enough Free Memory to Update Display" Error Message

Article translations Article translations
Article ID: 142931
This article was previously published under Q142931
This article has been archived. It is offered "as is" and will no longer be updated.
Novice: Requires knowledge of the user interface on single-user computers.

Expand all | Collapse all

Symptoms

When you run Microsoft Access for Windows 95 version 7.0, you may receive the following error message:
Not enough free memory to update the display.
This error can occur at different times, for example:
  • When you open a database with a startup form (as specified in the Startup options on the Tools menu).
  • When you use a main form with a subform control that has its NavigationButtons property set to Yes.
  • When you change Windows system settings (such as fonts, printer drivers, colors, and so on) while a main form with a subform that contains navigation buttons is open.

Resolution

The resolution is dependent on the action you were performing at the time you received the error message:
  • If you receive the error message while opening a database with a startup form, you can use an AutoExec macro to open the form instead of the Startup options on the Tools menu. To do so, follow these steps:
    1. On the Tools menu, click Startup.
    2. In the Startup box, under Display Form, select the (none) option.
    3. Click OK to close the Startup box.
    4. In the Database window, click the Macros tab, and then click New.
    5. Create the following new macro:
                Macro Name    Action
                ----------------------
                AutoExec      OpenForm
      
                AutoExec Actions
                ----------------------
                OpenForm
                   Form Name: <form name>
      						
    6. Close and save the AutoExec macro.
    7. Close and reopen your database. The AutoExec macro should open your startup form automatically when you open the database.
  • If you receive the error message while using a subform with the NavigationButtons property set to Yes, you can turn off the NavigationButtons property and add custom navigation buttons using the Command Button Wizard. If your subform is displayed in Datasheet view, you also need to change the DefaultView property to Continuous Forms. To do so, follow these steps:
    1. Open your main form in Design view and delete the subform control. Note that this deletes only the control, not the actual subform object which is listed under Forms in the Database window.
    2. Switch to the Database window, click the Forms tab, and then click New.
    3. In the New Form box, select the AutoForm: Tabular Wizard, select the table or query where the object's data comes from, and then click OK.
    4. View the new form in Design view, and then set the following form properties:
                DefaultView: Continuous Forms
                NavigationButtons: No
      						
    5. Use the Command Button Wizard to add four new command buttons to the form footer section. In the Command Button Wizard, under Actions, select one of the following actions for each command button:
                Go to First Record
                Go to Last Record
                Go to Next Record
                Go to Previous Record
      						
    6. Close and save the new form as NewSubformTest.
    7. Switch to your main form in Design view, and then drag the NewSubformTest form from the Database window to the main form and drop it in the former location of the original subform.
    8. Customize the subform control as appropriate; for example, set the LinkChildFields and LinkMasterFields properties.
    9. Save your main form and switch the form to Form view. The subform control should simulate a form Datasheet view.
  • If you receive the error message after you change Windows system settings while a mainform/subform that contains navigation buttons is open, you should quit Microsoft Access and restart the application. The best workaround for this situation is to quit Microsoft Access before you make any system changes.

Status

Microsoft has confirmed this to be a problem in Microsoft Access 7.0.

Properties

Article ID: 142931 - Last Review: October 26, 2013 - Revision: 2.0
Keywords: 
kbnosurvey kbarchive kbbug kbenv kberrmsg KB142931

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com