A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"There isn't enough memory to perform this operation"



 
 
Thread Tools Display Modes
  #1  
Old August 19th, 2008, 09:58 PM posted to microsoft.public.access.tablesdbdesign
Leon
external usenet poster
 
Posts: 65
Default "There isn't enough memory to perform this operation"

Hi,

I'm getting the above message while working in Access, even though the
computer isn't operating anywhere near its memory capacity. It's a fairly
large app -- about 72 MB of program with tables linked to another Access file
with ~200MB of data.

I have one very big form that reached its limit of allowable number of
controls, and this also gave us this message, but I took several controls off
(over a year ago) and the current problem seems unrelated -- I most recently
opened the app, opened a completely different form in Design mode and made
one slight change and got this error message. I hit the Okay button on the
dialogue box and the same dialogue box immediately reappeared. I had to shut
down Access via Task Manager.

I reopened the app, opened the same form in Design mode and it was
completely fine, but often the form disappears from the database, or won't
allow me to open it in Design mode or runtime. Sometimes when the form
disappears its code module can still be seen in the code window, but cannot
be opened or deleted.

I'm not at the size limit of anything I know about for Access, and would
really appreciate some help with this problem.

Thanks!
  #2  
Old August 19th, 2008, 10:44 PM posted to microsoft.public.access.tablesdbdesign
Jeff Boyce
external usenet poster
 
Posts: 8,621
Default "There isn't enough memory to perform this operation"

Leon

Make a backup copy. Make another. Maybe make a third!g

Run Compact & Repair on one of the copies. Does that change the size of the
file?

Make backup copies of the back-end. Run Compact & Repair on that
file(copy). Any difference?

Regards

Jeff Boyce
Microsoft Office/Access MVP


"Leon" wrote in message
...
Hi,

I'm getting the above message while working in Access, even though the
computer isn't operating anywhere near its memory capacity. It's a fairly
large app -- about 72 MB of program with tables linked to another Access
file
with ~200MB of data.

I have one very big form that reached its limit of allowable number of
controls, and this also gave us this message, but I took several controls
off
(over a year ago) and the current problem seems unrelated -- I most
recently
opened the app, opened a completely different form in Design mode and made
one slight change and got this error message. I hit the Okay button on the
dialogue box and the same dialogue box immediately reappeared. I had to
shut
down Access via Task Manager.

I reopened the app, opened the same form in Design mode and it was
completely fine, but often the form disappears from the database, or won't
allow me to open it in Design mode or runtime. Sometimes when the form
disappears its code module can still be seen in the code window, but
cannot
be opened or deleted.

I'm not at the size limit of anything I know about for Access, and would
really appreciate some help with this problem.

Thanks!



  #3  
Old August 25th, 2008, 05:18 PM posted to microsoft.public.access.tablesdbdesign
Leon
external usenet poster
 
Posts: 65
Default "There isn't enough memory to perform this operation"

Yes,

Our method of dealing with the problem so far is saving a lot and Compact &
Repairing a lot. See my re-post from today (I didn't realize this one had
actually gone through) for more details about what happens to the app's size
when we run Compact & Repair (and when we just open the Forms). Haven't tried
compacting and repairing the datafile, but that seems like a stretch since
the problem happens when working on forms in Design mode, without ever
leaving Design mode (so not ever really seeing the datafile). But I can give
it a try


"Jeff Boyce" wrote:

Leon

Make a backup copy. Make another. Maybe make a third!g

Run Compact & Repair on one of the copies. Does that change the size of the
file?

Make backup copies of the back-end. Run Compact & Repair on that
file(copy). Any difference?

Regards

Jeff Boyce
Microsoft Office/Access MVP


"Leon" wrote in message
...
Hi,

I'm getting the above message while working in Access, even though the
computer isn't operating anywhere near its memory capacity. It's a fairly
large app -- about 72 MB of program with tables linked to another Access
file
with ~200MB of data.

I have one very big form that reached its limit of allowable number of
controls, and this also gave us this message, but I took several controls
off
(over a year ago) and the current problem seems unrelated -- I most
recently
opened the app, opened a completely different form in Design mode and made
one slight change and got this error message. I hit the Okay button on the
dialogue box and the same dialogue box immediately reappeared. I had to
shut
down Access via Task Manager.

I reopened the app, opened the same form in Design mode and it was
completely fine, but often the form disappears from the database, or won't
allow me to open it in Design mode or runtime. Sometimes when the form
disappears its code module can still be seen in the code window, but
cannot
be opened or deleted.

I'm not at the size limit of anything I know about for Access, and would
really appreciate some help with this problem.

Thanks!




 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 07:20 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.