There isn't enough memory to perform this action

[Terry Holland]

Im having some problems with an Access 2003 db that I do occasional
maintenance and updates to.

I have create a new form and progress has been really slow. The main reason
is that each time i added a text box without an accomanying label, Access
crashed. It took me a while to realise what was causing the problem but
since then, I have been adding text boxes and hiding labels and access seems
to tolerate this.

Now however, I cannot open the form at all, either in design or normal
view!!! Any attempt to do this results in the error "There isn't enough
memory to perform this action"

I have tried creating new db and importing all objects but my new form will
not import.

Ive tried using the SaveAsText and LoadFromText function but when I attempt
to use SaveAsText on new form I get the error "Microsoft Office Access has
encountered a problem and needs to close...." and Access closes.

This is infuriating. A relatively simple task is taking up hours of time
and consequently I am losing money by the hour. I have searched web for
solutions to this but up to this point I have not found a solution.

Im developing on a XP Pro SP2, Office 2003 SP3 machine.

tia for any pointers

 

[Allen Browne]

Terry, I have seen this problem with A2003.
Leaving the attached label hidden is sensible workaround.

From memory, I don't think the bug is fixed by the hotfix, but you probably
want it to fix other issues in SP3 anyway:
http://allenbrowne.com/bug-Access2003SP3.html

 

[Terry Holland]

I discovered this and started doing this and it seemed to resolve the problem
for a while. I then started adding other controls onto the form (buttons and
labels) saving ever couple of mins. The last time I attempted to save,
Access crashed and not I cannot open the form at all - either in design, or
normal mode.

Am I to assume that this form is now lost or are there any other tricks to
retrieving (other than the ones I already tried)

Terry

 

[Allen Browne]

Try exporting the form to a text file.

1. Make a backup of the MDB so you get multiple repair attempts.

2. If you can open the code window and see any code from this form, copy the
code and paste into Notepad.

3. Compact, decompile, compact.
If you are not sure how to decompile, see:
http://allenbrowne.com/recover.html

4. Open the Immediate Window (Ctrl+G), and try:
SaveAsText acForm, "Form1", "C:\MyFolder\MyForm.txt"
using your own form name, and a suitable folder.

5. If that works without error, delete the form, and compact the database.
Then try importing the form from the text file:
LoadFromText acForm, "Form1", "C:\MyFolder\MyForm.txt"

For a badly corrupted form, this may not work. In that case, import an old
copy of the form from backup. You may even be able to paste in the code from
step 2 above if you have modified that recently.

 

[Terry Holland]

I have previously tried the SaveAsText method but i didnt do a decompile
before. DO you think this will make a difference? If you think so I will
try this this evening

Terry

 

[Allen Browne]

Terry, I doubt the decompile first will make a difference to the SaveAsText.

If the problem is with the binary associated with the form, the decompile
will address that. Worth a shot, but my guess would only be around a 1 in
10 chance of that making the difference here.

 

[Terry Holland]

Allen

I wasn't able to recover my form. I tried the decompile but system still
crashed when attempting to SaveAsText. On your link to decompile, you
mention that the
Name AutoCorrect is know to cause some problems. I unticked this and
recreated my form and things seem to be more stable - ie system has not
crashed since doing this. May be coincidental or it may be responsible for
more problems than you list on your site.

Thanks for your input

 

[Allen Browne]

.... On your link to decompile, you mention that the Name AutoCorrect

is known to cause some problems. I unticked this and recreated
my form and things seem to be more stable - ie system has not
crashed since doing this. May be coincidental or it may be
responsible for more problems than you list on your site.

So another one goes down to Name AutoCorrupt, eh?

Yes, that certainly is responsible for more corruptions than I list. There
have been so many, I don't try to maintain that list any more. Some have
been fixed, and others uncovered. The list is just enough to provide a
warning.

Many of the real issues (yours included) are probably a combination of
factors, such as a bad binary + a bad Name AutoCorrect dependency.

Anyway, it's something you *always* want to turn off.