Not enough memory to perform operation - Tried to install V-Tools/Rick Fisher

[crobaseball]

Hi, I'm getting an error when trying to run a report. "There isn't enough memory to perform this operation. Close unneeded programs and try the operation again." Here's what has happened recently that may be my issue:



1.) I tried to install both the V-Tools and Rick Fisher add-ins, and neither one could be added. I got errors from both.

2.) I'm working with a small test database to create a report. Db is tiny, 1.8Mb. But I've also created a report which has several embedded subreports. Everything is based off of queries which certainly have to sort through some data.

3.) I have compacted and repaired.

Help!!! This is really slowing me down trying to get this project completed

[crobaseball]

I just tried to rebuild the form in case I had corruption. I also rebuilt one of the sub forms. Same deal. Need help . . .

[John_G]

Hi -

"The db is tiny" - does that include the data, or are you using liked tables?
Do the queries work OK if run by themselves in Query design?

One thing to try is run the main report with one of the subreports removed, and removing a different subreport each time. You might be able to isolate the problem to one subreport.

Let us know how it goes.

HTH

John

[crobaseball]

Hi -

"The db is tiny" - does that include the data, or are you using liked tables?
Do the queries work OK if run by themselves in Query design?

One thing to try is run the main report with one of the subreports removed, and removing a different subreport each time. You might be able to isolate the problem to one subreport.

John

I think you meant linked tables, but yes it does indeed include all the data. I'm testing, so I have a very small amount of test data I'm working with. This is part of what has me so worried. What happens when I upload a couple thousand records?

The queries all run very, very quickly. The report which is blowing up has one main subreport which does not open very quickly. In it, there are 3 more embedded subreports. I get the "thinking circle" for what I counted as 4 secs. I did as you suggested and removed each one, then re-ran the report. The "thinking" time reduced to roughly 2 secs, but none of the embedded subreports sticks out as loading particularly slowly (I tried each combination). I then ran the actual subreports themselves, and each of the 3 loads very quickly. No "thinking circle".

Have you ever heard of a failed add in causing corruption to access itself? Do I need to reinstall Access?

[crobaseball]

I just tried the report on our network, and the same memory error is coming up. So clearly there's something in my architecture of the report that is causing this to blow up. I'm so frustrated that the queries work great, but that something is clearly afoul in the actual reports/subreports.

[June7]

Do you want to provide the db for analysis? Follow instructions at bottom of my post.

[orange]

crobaseball,

I agree with June7, post a copy for readers to review/analyze. We can only guess at your situation, but having access to some data in context (eg a copy of the db with personal info removed) would help.

[crobaseball]

Ok, here we go. Nothing of big privacy concern, so here's a copy.

One thing I noticed: I had a much longer list of the "suppliers", which is the most overarching of the categories. When I removed many of these, the error disappeared. But I'm afraid that when I add them back, along with the specific item/color/carton information which they are associated with, I'll come back to the same issue.

One way or the other, here it is.

And thanks ahead of time for the help!

One last small thing: I have made some changes since then, creating more queries and adding data, so the original size of it has grown very quickly to just over 8MB

[June7]

Compact & Repair reduced file size to 2MB.

I opened every report without issue.

[crobaseball]

Like I said, I reduced the number of suppliers, and it came up fine. As I begin to upload the data, I'm curious to see if I'll start to have probs. I'm sure hoping not.

[crobaseball]

MOD EDIT: merged threads

I have what I would think is a relatively small database. 6 tables with relationships, 15 odd queries. And I'm getting the "not enough memory to perform operation" when I try to run a report. The things I would consider to be "strange": 1.) The report has embedded subreports. It has one which has one more embedded subreport. 2.) I have a memo field which is in there, which I have to have to denote things which are particular to items.

I have repaired and compacted the db several times. Nothing seems to help. The scary part is that I've only loaded about a third of my data. This is only going to get worse as I increase the number of suppliers/series, etc.

Also, I have attached the actual db itself for anyone to take a look at.

Help!

[June7]

Weird. I could reset links to all tables except Series (as well Name AutoCorrect Save Failures which seems irrelevant - why does this show as a link anyway, there is no such table). Keep getting '\\DMI...' is not a valid path...

I deleted the link. I created new table in Master and copied the Series records, deleted the original table, renamed the copy. Recreated link in Sales. As afterthought, deleting and recreating link might have been sufficient.

Opened and closed each report until I got to Sales_Pricebook_Suppliers and hit "Cannot open any more databases". Never encountered this before. Had to press Ctrl+break to kill the warning then the report opened. Same for Sales_Pricebook_Suppliers_DealerAOnly.

However, opening directly to PrintPreview instead of ReportView does not error.

[crobaseball]

I'm a little stumped myself. Ok, a lot stumped. Nothing seems extreme. But this is only going to get worse. This is one supplier (albeit our largest, hence the 1/3 of the total data in the "Lines" table), and I have 25 more to add. Those 25 suppliers then average 10 series which they are connected to. And then we throw in the actual Lines . . . So the complexities of the links will only grow.

Are there other resources I might be able to tap into? I'm running this off of a server, and I'm a little surprised there are issues there. This IS the 32 bit version. Is this my prob?

[June7]

At this point, I can only suggest not opening in ReportView.

Tracking down cause may be beyond my abilities and too time consuming anyway. Would start with rebuilding the two reports. Adding subreports one at a time and test opening report until failure. I just noticed you have already tried this.

Did these reports run fine before try to add in VTools and Fisher's Find & Replace? I never had issue with Fisher's add-in, but have not tried with my new Windows 7 64-bit computer with Access 2010. Maybe reinstall Access couldn't hurt.

[crobaseball]

I rebuilt the whole thing. And it's blowing up still. I'm so frustrated . . . would the memo field have anything to do with it? Not a ton of information in there. I can't get the page break controls to work either.