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-21T19:42:26+00:00

    Hi Skirk_70,

    > The issue is if the continue to use it over the day or days. The memory keeps climbing until there is none available.

    You might want to ensure that you are properly closing DAO recordsets, and setting the recordset variable = Nothing at the end of procedures. Also, make absolutely sure you are not opening a DAO recordset, or using CurrentDB within a loop; those kinds of programming snafus are sure to consume precious memory, and not release it in a timely manner.

    You may have been close to the edge before, but just below the critical memory threshold, with previous versions of 32-bit Access. Then, along comes a new build that needs just a bit more and the apple cart tips over.

    If you are not sure what I mean by properly closing DAO recordsets, and setting variables = nothing, then do post back. I can post a generic example.

    Was this answer helpful?

    0 comments
  2. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-21T18:56:15+00:00

    We've pinged the MS Access team again. Keep the pressure on by posting here and maybe by going to our new Access site and adding comments and support. Karl's goal is to raise visibility of bugs and potential bugs in order to facilitate communication with MS.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-21T18:47:04+00:00

    Tested using Sql Server 17 & 19 with the same results.

    We are now at over 30 different customer sites that have had it. As soon as we remove the update they are good.

    The key thing I see is that queries run and memory use grows for Access which is normal. The issue is that it never releases and continues to grow with each new process until all virtual memory is used up.

    Was this answer helpful?

    0 comments
  4. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-21T18:03:15+00:00

    Preliminary test using the SQL Server driver showed the same performance for me. I.e. I see little to no increase in Memory Usage in Task Manager and return a cartesian query recordset of over 9.6 million records from a remotely hosted SQL Server with what I consider to be a typical time lapse for a recordset that large.

    I still need to test inserts and updates as well as straight selects, but there's still no confirmation of a reason some people experience this.

    Maybe we should be looking at SQL Server versions as well? The one I'm using is SS 2019.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-12-21T11:01:08+00:00

    Hi,

    On Premises. Here is a connection string example.

    ODBC;DRIVER=SQL Server;SERVER=sqlpc2\sql2019;DATABASE=PT;UID=PTUser;PWD=abc;

    Have you already tried if the problem goes away with a different ODBC driver?

    I ask mainly because in November it was reported that Microsoft screwed up the old SQL driver coming with Windows. I haven't read any reports yet that Access users couldn't connect, but maybe there's a relation here.

    Servus

    Karl

    Was this answer helpful?

    0 comments