Forum Discussion
Preview report out of memory error with Access Version 2609 (Build 20430.20092)
We have multiple customers reporting issues with latest Access version 2609 Build 20430.20092 when previewing reports.
(2004) There isn't enough memory to perform this operation. Close unneeded programs and try the operation again.
This error seems to occur right when we preview a report and the report will not open. At the moment, we have been rolling Office back to version 2608 to resolve the issue.
10 Replies
- JasposTin Contributor
I had this same issue when my PC updated to the new office version on Fri (on the current channel, not pre-release)
But I found a fix (for my main DB at least)
If you cannot revert back your office version, this simple fix worked for me - if you have your DB set to having a custom icon for your application AND form and reports, in settings simply uncheck the box saying 'Use as form and report icon. You'll lose custom icons on your forms and reports, but, for me at least, it fixed the issue with the memory error on reports, and my Access app is back and fully working.
- HansiFlickerCopper Contributor
Hey Karl_Donaubauer, do you have any updates? We have multiple customers having the same issues. is there a fix availible soon? many thanks for your reply.
Hi,
A fix is on the way but it is still not sure if it will be included in the next Current Channel update in a few days or come later.
Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK 10./11.10. NürnbergHi,
I have now got the information that the fix will be included in tomorrow's Current Channel update, which should be build 16.0.20430.20144.
Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK 10./11.10. Nürnberg
- andybentley52Copper Contributor
I have the same problem, but it only appears to effect databases with the .accdr extension.
Identical database but with .accdb works ok. Hi,
There have been several reports about this for version 2609 in the last 10 days, e.g. on Q&A.
This looks like a recurrence of an older problem. According to one report the old workaround from back then also helped in his case:
If you open a second (dummy) report before previewing a report the error should not occur.
An MVP colleague informed Microsoft about the problem today. If I hear any updates, I’ll share them here.
Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK 10./11.10. NürnbergHi,
Microsoft is working on a fix for this bug. I'll keep you updated.
Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK 10./11.10. Nürnberg- RJBrenemanTooTin Contributor
It's related to the app using an icon in Options, Current Database, but there are other factors we couldn't pin down. Rolling back to 2608 fixes the issue as does opening a dummy report first.
- George_HepworthSilver Contributor
Can you provide a sample database that reliable reproduces the issue?