Microsoft Access Memory Issue after December 6 2022 Build15831 Office Update

Anonymous
2022-12-13T20:25:43+00:00

I've found that Access programs are running out of memory or getting system resources exceeded errors after the recent office update. If I open task manager and watch the memory resources the continue to go up and are never released like they normally do. This was not an issue until the update last week. Working in O365 32 bit access.

Anyone else experiencing this?

Microsoft 365 and Office | Access | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

69 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-12-19T19:24:18+00:00

    Hi Tom, yes we use redemption for emailing. It is very much active a really a great product. I'll be sure to take a spin around the FMS product to see if there are advantages to it.

    Thanks

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-17T17:10:42+00:00

    Correct me if I’m wrong, but isn’t “redemption” the older product “Outlook Redemptiin”? I’ve never used it, but I think it assists with automatically dealing with the various security prompts that Outlook pops up when using automation from other VBA-enabled applications such as Access and Excel.

    Is the product still being actively maintained (I honestly don’t know)?

    Have you considered switching to a method that uses an independent SMTP engine, so that when the Outlook team makes changes to the security model, it does not possibly break your application? One possibility, which I have used with good success is FMS’s Total Access Emailer software. You can purchase a developer license that covers any number of Access projects for multiple customers. Something to consider…

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-17T16:59:43+00:00

    You’ve taken the prudent action by changing to the semi-annual update option, in my opinion. No point suffering continual “paper cuts” if there isn’t a need to be on the bleeding edge!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-17T16:47:29+00:00

    Thanks for the update. We had about a dozen sites get hit with the issue this week. We adjusted them to semi-annual or monthly update channel which rolls the update back and that resolves it.

    I would add that I’ve observed that it tends to happen more when dealing with large datasets.

    Hoping this resolved before the next round of updates hits more of my customers.

    Was this answer helpful?

    0 comments
  5. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-17T16:30:13+00:00

    Unfortunately, after the first day on which I observed queries exhibiting this problem, I've been unable to replicate it since, using both remotely hosted SQL Server database tables and local SQL Server database tables.

    Here's a link to the blog post describing my experience.

    I'm not ready to conclude that there is no problem, or that it's the result of a bug in an Update. It's just that having failed to replicate it on several different occasions, I'm leaning more towards something that happened temporarily for some people.

    Please keep this thread updated if you see the same problem appear, or re-appear.

    Was this answer helpful?

    0 comments