Access 2007 - Vista - There isn’t enough memory error

[Curtis Stevens]

I'm receiving several different memory error messages. It fixes to restart
the computer, but its happening all the time. I'm not sure what causes it,
don't think it is any one thing. My database was originally 2002, I tried
using that one, but went ahead and created a new 2007 copy by importing
everything into it. Everything worked perfectly in 2002 on my old computer
running XP, never any issues at all!

I also installed office 2007 service pack1 along with the hot fix that fixes
the slow performance when dealing with 2002 or earlier database versions.

It doesn't seem to matter what I'm doing, whether it is opening a form via a
button or running a small query. BUT once I get the first error message, I
can't do much in my database without errors until I restart the computer.
Closing and reopening access doesn't seem to work. I tried rebooting and
only open Access and then open a few forms, do that, do this, nothing more
complex (program or code wise) than clicking on a button for a form to pop up
and I can get it to start doing it fairly easy. It isn't one thing that
starts causing it from what I can trouble shoot.

Error messages:
"There isn’t enough memory to perform this operation. Close unneeded
programs and try the operation again."
"Run-time error 2004"

I have 4 gigs of DDR2 800 MHZ memory.
This is a single Database locally on my computer, not on a network.

Thanks
Curtis

 

[Paul Shapiro]

Every time I've seen the "not enough memory" error it's actually a corrupted
Access object, usually a form.

Try creating a new blank db and importing all your objects. If that doesn't
fix it, try to narrow it down to which object(s) are corrupted, and replace
those from an older backup or rebuild them.

 

[Curtis Stevens]

As I mentioned in my post, I already tried creating a new db and importing
everything. I ran the compile feature on visual basic, to see if there were
any errors. My confusion is how come it works perfectly in 2002 version, but
gives me this trouble with a newer 2007 version?

 

[Paul Shapiro]

Sorry, I didn't read carefully enough. Since you didn't mention the outcome,
I assume the compile succeeded without errors? If the compile has errors,
check the VBA references to see if any are missing.

I would still guess it's corruption. Is this a split db? If not, try
importing just the tables first. If the db is ok, or it's split, then try
importing all the queries. Test enough of them that you're comfortable
things are ok. Then it gets harder if your forms need code from modules. So
next try importing either the forms or the modules. Etc. See if you can find
a baseline that works ok, and then identify what breaks it.

 

[a a r o n . k e m p f]

JET is the cause of corruption.

get rid of Jet and MS Access runs like a charm.

Access Data Projects are the preferred way to build multi-user
applications using Microsoft Access.