IMMEDIATE! Access error 2004 There isn't enough memory to perform this operation

COW Farmer 40 Reputation points
2026-09-15T20:04:12.8666667+00:00

It appears that the same issue from June 2023 is happening again. At that time I posted the following to the MS Community the issue being experienced by numerous clients.

KB5026446 seems to cause Access error 2004 There isn't enough memory to perform this operation

7 days later, MS put out an update to correct the situation they caused. They need to do the same, ASAP. Could you please let the community know when this situation will be resolved and any work-arounds for the time being. Thanks you.

Microsoft 365 and Office | Access | For business | Windows
0 comments
Answer accepted by question author
Karl Donaubauer 3,661 Reputation points MVP
2026-09-16T19:23:43.2866667+00:00

Hi,

I joined the Microsoft 365 Insider program and was able to download and install the pre-release version 2609 Build 16.0.20430.20032

Nobody with a productive application should be in this channel and have this version and build. The Preview channel is for test purposes only. See our description and recommendation in the AFo article about update channels. It also provides instructions on how to change channels.

Please advise how to revert back to the previous version of Microsoft Access.

Roll-back to previous versions of Office

Servus
Karl

Access Forever News DevCon
Access-Entwickler-Konferenz AEK 10./11.10. Nürnberg

Was this answer helpful?

1 person found this answer helpful.
Answer recommended by moderator
COW Farmer 40 Reputation points
2026-09-17T15:06:34.2766667+00:00

Simply changing the channel will not resolve the issue but is still very important so it doesn't update again once you've fixed the problem. The easiest way to correct it is to revert back using the office deployment tool:

https://support.microsoft.com/en-us/office/lifecycle/how-to-revert-to-an-earlier-version-of-office

I used the parameters for the June 9, 2026 Semi-annual Enterprise Channel<Updates Enabled="TRUE" TargetVersion="16.0.19127.20678" /> and everything seems to be working properly.

Microsoft, please make sure this issue does not make it's way to an official release.

Was this answer helpful?

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. George Hepworth 23,120 Reputation points Volunteer Moderator
    2026-09-15T20:24:29.89+00:00

    Yours is the first report of this issue I've seen.
    Four things will help build a case to share with the Access team.

    Your version and build. Run from the immediate window:
    ?syscmd(acSysCmdGetFullVersion)
    Microsoft Access (Version 2608) Build 16.0.20326.20144 Current Channel 32-bit

    A description, including screenshots if possible, of the exact process which raises the error.

    An ACCDB which reliably reproduces the behavior, if you can share it, would be very helpful.

    Thank you.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.