Microsoft Knowledge Base Email Alertz

You receive an out of memory error message in Access 2003 and Access 2002 when you use grouped controls

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: 907836 - Last Review: January 8, 2007 - Revision: 1.3

You receive an "out of memory" error message in Access 2003 and Access 2002 when you use grouped controls

SYMPTOMS

In Microsoft Office Access 2003 and Microsoft Access 2002, if you repeatedly open and close a form that includes grouped controls in one session, you receive the following error message:
Run-time error '2004'. There isn't enough memory to perform this operation. Close unneeded programs and try the operation again.

WORKAROUND

To work around this issue, ungroup the controls. To do this, follow these steps:
  1. Open the form or the report.
  2. On the View menu, click Design.
  3. Click any control in the group to select the group.
  4. On the Format menu, click Ungroup.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

APPLIES TO
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition
Keywords: 
kbharmony kbprb kbexpertiseadvanced kbexpertiseinter kbtshoot KB907836
       

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

Anonymous User Report As Irrelevant  
Written: 3/27/2008 4:13 PM
I'm getting this error not for grouped controls, but after I replace a subform on a form with a different one, then try to open the form.

Leslie Report As Irrelevant  
Written: 5/8/2008 11:31 AM
And I get this error after users open the form and close it multiple times but there are no grouped controls. There are subforms and the form has tabs on it. But I can't find anything to fix this problem other than to replace it with a backup copy of the database.

Anonymous User Report As Irrelevant  
Written: 6/18/2008 6:42 AM
I created a large database for work (forms with subforms and tabs, query based forms, command buttons, but very little VB as I don’t know it). The FAT client shortcut points to mdb file on the server, and it falls over at different points (mostly when saving form development, but sometimes when user navigating, and not always in the same place). I re-developed it from scratch on my home PC, and it has never fallen over on it, but have periodically copied over to my work PC, and sooner or later it does. IT dept cannot pin-point the prob but have suggested it is down to programming - although a 2 table dbase with a simple 1-many relat I later built - with no VB, command buttons, etc - also fell over at work. I activated the auto compact & repair option as suggested elsewhere, but it corrupted the visual content of a combo box, and I had to revert to an earlier copy and bring up to speed. I still haven’t found a solution.