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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-03T19:08:01+00:00

    Hi Tom,

    > I don't see a practical use for it on 64 bit.

    The practical use being able to show a reluctant client the “before and after”.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-03T12:42:06+00:00

    Hi,

    We are experiencing the same issue with 32-bit access.

    We have a quarterly report which last ran successfully at the end of September.

    We noticed the out of memory issues late last year whilst we were preparing for the report run this week.

    We rolled back the database to the last run which worked and the issue still persists. Which points to the December patch.

    We can consistently re-create this issue if this would be helpful for troubleshooting the problem.

    Once this quarters reports are done, we will try running in 64-bit access to see if that resolves the issue.

    Stuart Turner

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-12-24T09:26:34+00:00

    Hi Tom,

    > I realize the intent is to show how virtual memory can become starved in 32-bit Access

    Exactly. That's the only reason I've used it. I don't see a practical use for it on 64 bit.

    IIRC Mike's attempts to get reasonable data from it on 64 bit were not successful so far.

    Servus

    Karl

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-12-23T21:15:07+00:00

    ... 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.

    Hi Karl,

    Any chance you can add conditional compilation to your sample download at AUGET, so that the sample that includes a call to the GlobalmemoryStatusEx API can run in both 32-bit and 64-bit Access? It currently only compiles in 32-bit Access. I realize the intent is to show how virtual memory can become starved in 32-bit Access, but it would be nice to be able to easily run side-by-side comparisons of databases with problematic busy forms using both 32-bit and 64-bit Access.

    I took a stab at converting it, but there doesn't seem to be much information on the web for converting this to 64-bit. I found a version that Mike Wolfe has posted in this article, but unfortunately his version fails to compile in 32-bit Access. I have notified Mike of this problem.

                    64-bit Unsigned Integers in VBA

                    Nov. 22, 2021

                    https://nolongerset.com/64-bit-unsigned-integers-in-vba/

    Tom

    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