Out of Memort Error -- Frustrated!!!

M

MJ

Can one of you help me understand what seems to be happening and/or how to
fix it?

ERROR: "There isn't enough memory to perform this operation. Close uneeded
programs and try the operation again."

I am running Ac2003 (Office 2003 SP3) on WinXP Pro (SP2). I am maintaining
two databases for two teams within my office doing the same sort of
operations.

I was tasked to change the questions on an audit form in both databases. I
have made the adjustments in parallel and at COB last night I had one working
and was working on completing the adjustments to the other database. This
morning both databases came up just fine, completing the changes in the
second db, when I decided to do some minor clean-up in the first one,
changing some of the subroutine names to standardized them with the others in
both dbs. All that and I tried to open the form and it blew up with this
memory error.

This is the second time this has happened to this SAME database. The same
changes in it's sister database have not caused any problems so far.

Does anyone have any ideas?

Thank you in advance.
 
G

GBA

I have run into this one time - and in my case I concluded it was faulty PC.
I would reboot - and then it worked fine. Occurred randomly on only 1 pc -
and in each case a reboot cleared it.

Never truly fixed.
 
J

Jack Leach

I started having the same issue recent runing Access 2003 on WinXP as well.

I don't know what might be causing the issue (I can't imagine Access using
the entire RAM and pagefile even in the most complex of loops or queries),
but my first suspect would be some sort of db corruption. In which case QB's
suggestion is usually the best place to start.

You can try and pinpoint if a certain process in the app is doing this...
ctl+shft+esc will pull up the task manager and you can moniter cpu
performance while you play around in this db and see if you notice any
trends. The performance analyzer under ControlPanel -> Adminstrative Tools
might harbor some clues as well.

I'm assuming that you guys have done the obvious and are using adequate
computers without tons of high overhead apps running the the background

If seem to pick anything up with this and don't know where to go with it
post back, maybe a few clues might jog someone's memory.

I also run '03 on various versions of XP and (as of yet) have never run into
this problem. Hopefully it stays that way.

Hopefully this is just a (fairly) simple case of access accidentally
screwing up some naming in the background and importing everything to a new
db works for you.

--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)
 
C

Clifford Bass

Hi,

I presume you have tried compacting and repairing? Have you tried the
decompile/recompile? If not, see
<http://www.granite.ab.ca/access/decompile.htm> for how to do it.

You mentioned that you were making changes to a form. By any chance
does that form have a lot of controls (text boxes, buttons, labels, etc.)?
Some time back I ran into an issue with a form when I got up around 1,000
controls. The error I got, which I no longer remember, did not give a clue
that the real problem was too many controls.

Hope that helps,

Clifford Bass
 
L

LloydBrown

This reminds me of an error I got a few years ago. The solution was to turn
off the
Track name Autocorrect option under tools, options, General tab. You won't
be able to change field names without tracing all the references by hand
after that, so try it in a copy first.
 
T

Tony Toews [MVP]

Clifford Bass said:
You mentioned that you were making changes to a form. By any chance
does that form have a lot of controls (text boxes, buttons, labels, etc.)?
Some time back I ran into an issue with a form when I got up around 1,000
controls. The error I got, which I no longer remember, did not give a clue
that the real problem was too many controls.
Click to expand...

There can also be a similar problem with a very large number of
controls that have been created and deleted on a form. Presumably
importing it into another MDB would solve that problem.

Tony
 
T

Tony Toews [MVP]

MJ said:
Can one of you help me understand what seems to be happening and/or how to
fix it?
Click to expand...

This is MS Access's message when it doesn't know what the problem is.
(Maybe it should be renamed to What the frig?)

I'd suggest importing all your objects into a new MDB and see if that
fixes things.

Tony
 
C

cujocon

I am currently having the same issue "OUT OF MEMORY" is the only message.
The db is running on a terminal server with plenty of RAM. I've done
everything listed above...turned off autotrack, decompile, rebuilt db from
scratch. The form that is causing this isn't huge - about 100 controls. I
can add controls without error up to a point, then it's like the straw that
broke the camels back...I go into the code hit compile and "OUT OF MEMORY".
Go back to the form, remove the control...and it's fine. Seems like Access
is self limiting the memory use or something. Would love some more
advice...this is killing me.
 
C

Clifford Bass

Hi,

One hundred controls is a small number. If you copy the database to
your computer or someone else's and try it there, do you still get the
out-of-memory? Also, when you say that there is plenty of RAM, is that on
the physical machine or what Terminal Server is allocating to you? If my
understanding is correct, it can be configured to allocate much less to each
session.

Clifford Bass
 
C

cujocon

I'm looking into the user allocation issue now...I'm copying the db to my
local machine to see if it works outside of Terminal Services. I do still
get the error on a different pc...and others get the same error when
attempting to compile the code.
Thanks for your help.
 
C

Clifford Bass

Hi,

Not sure I've been much help there. If none of the suggestions by
both me and the others have helped, I am not sure what you can do. One final
thought: Could it be related to the control types? Are these all simple
controls such as text boxes and labels? Or are there a fair number of image
and/or OLE and/or ActiveX controls?

Clifford Bass
 
C

cujocon

they are pretty standard text boxes, check boxes, and drop down lists. I
have other forms in the same db that are much larger that don't get the same
error. I'll post once I can verify that it's not a memory allocation
issue...need to hear back from admin on that.
 
S

Stuart McCall

cujocon said:
I am currently having the same issue "OUT OF MEMORY" is the only message.
The db is running on a terminal server with plenty of RAM. I've done
everything listed above...turned off autotrack, decompile, rebuilt db from
scratch. The form that is causing this isn't huge - about 100 controls.
I
can add controls without error up to a point, then it's like the straw
that
broke the camels back...I go into the code hit compile and "OUT OF
MEMORY".
Go back to the form, remove the control...and it's fine. Seems like
Access
is self limiting the memory use or something. Would love some more
advice...this is killing me.
Click to expand...

I don't know if this has been suggested, but it sounds like you've overrun
the form control creation limit (can't remember the exact figure, maybe 700
or so). This can happen when you create and delete a lot of controls on an
access form. Each control creation increments the creation counter (my
terminology), but when you delete a control, it is just hidden. Why the
Access developers decided to do it this way is beyond me.

I recommend re-creating this form at least partly, then paste in the code
and test. DON'T copy & paste any of the controls. If this fixes the problem,
continue till the whole form design view is replaced and, once you're happy
it's working, delete the problem form. Follow this with a compact.
 
J

JimfromIndy

I run in exactly that environment. I get the exact same "out of
memory" issues. I found two causes:

1. The copy/paste buffer in Citrix/Remote Desktop is not properly
cleared, and ends up filling up. There is a fix, but it's not a
permanent one. I end up rebooting the remote computer half the time.
You can manually clear the buffer, and it works for awhile, but
eventually, you just have to bite the bullet and reboot. Logoff
doesn't work for some reason.

2. Using "exotic" libraries like ADOX can also cause the same issue.
Nothing wrong with them, but if you have an error in your program, the
usual error trapping fails and your get the "OUT OF MEMORY" error. I
literally get it on compiles when I improperly declare ADOX objects.
Sometimes, I get it when I declare ADO objects incorrectly. Check your
dim statements and make sure they're proper and conservative.

Hope this helps

Jim
 
C

cujocon

Our ultimate resolution was to take a brand new instance of MS Access, copy
in all of the modules, forms, queries, reports, ... one section at a time,
compacting and repairing along the way. Once that was done we were able to
build the problem forms anew and keep working.
Thanks for all the help.
 
C

Clifford Bass

Hi Stuart,

Thanks for reporting back on the status of the issue. Glad you got it
resolved and glad to have helped to the extent I could.

Clifford Bass
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

"There isn't enough memory..." 1
Synchronize Error 3251 in Access 2007. 1
Opening a database via Citrix 7
Access 2003 On Open Event Error when 2007 installed 8
Out of Memory errors Using Access 2003 SP3 1
Error Message 2
Type mismatch error - Setting Hyperlink Base property 2
Database "Error" 2

Top