Microsoft Access Memory Issue after December 6 2022 Build15831 Office Update

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

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

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

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

Hi Stuart,

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.

As some affected users here and Georg wrote in our blog the reports point to several builds of version 2011 and the problem should disappear when you role back to version 2210 of Office 365. Since you have a reproducible scenario your findings with 64 bit could contribute to narrow it down.

Since SQL Server is involved and probably a lot of data, I assume you won't be able to provide a trimmed down sample DB+script or the like that we and Microsoft could use to reproduce the problem? Such reproduction data/files would be crucial for a fix.

Servus

Karl