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: Oldest
Most helpful Newest Oldest
  1. 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
  2. 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
  3. Anonymous
    2022-12-21T20:01:43+00:00

    Good point on this update being the tipping point. I believe I covered closing and setting recordsets to nothing but will take another pass through to make sure nothing was missed. Based on the feedback I'm not real optimistic they will release a fix anytime soon so I need to find a work around.

    Thanks for the feedback!

    Was this answer helpful?

    0 comments
  4. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-21T20:07:53+00:00

    I agree with one aspect, Tom. We don't really know for sure where the problem comes from.

    However, the fact that rolling back an update resolves the problem points at that as a contributing factor. Also, the reports we've seen all refer to queries, not opening recordsets per se.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2022-12-22T10:18:02+00:00

    Hi,

    Too bad it's not the driver ;-) We know so far O365 32 bit version 2011 different builds have it, with version 2010 it goes away. Different versions of Windows and different ODBC drivers are affected.

    What else could make the difference that it doesn't happen for all?

    @SKIRK_70 Are these really "pure" (select?) queries that you execute, or are they queries that are behind Access objects, i.e. forms or reports?

    If the latter, that might be worth another test, George, because the classical problems with virtual memory happen most often with forms.

    Servus

    Karl

    Was this answer helpful?

    0 comments