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-22T13:19:57+00:00

    Pure queries generated for testing. I ran one Update query, which didn't perform any different from the select queries.

    I will try the suggestion of incorporating some queries into a form today.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-12-22T14:42:03+00:00

    Hi George,

    The question was more directed to the people affected by the problem like SKIRK_70. It seems that in addition to the M365 version there is sth involved that we didn't detect so far.

    If the affected people would like to see more exactly when (and thus by what) their virtual memory is eaten up they could either use the external tool VMMap from Microsoft or some lines of VBA code using the GlobalMemoryStatusEx API.

    I showed both methods in the video already mentioned in this thread and all the material incl. the tool and sample code is still available in my downloads at AUGET. Maybe this helps to detect what's involved.

    Servus

    Karl

    Was this answer helpful?

    0 comments
  3. George Hepworth 23,120 Reputation points Volunteer Moderator
    2022-12-22T14:49:39+00:00

    It also finally just dawned on me to ask the various OP's if the less- and non-performant queries are aggregates (i.e. have group by clauses in them).

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-23T03:32:17+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.

    I think they need a good repro case, before they have much chance of fixing the problem.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-12-23T10:05:54+00:00

    Hi,

    > I think they need a good repro case, before they have much chance of fixing the problem.

    Yep. Meanwhile, affected folks might try whether setting the LAA switch (I linked some sources above) as workaround can delay the memory problems so far that they are able to continue running their applications.

    Servus

    Karl

    Was this answer helpful?

    0 comments