Microsoft Access Memory Issue after December 6 2022 Build15831 Office Update

Hi Tom, I met with our IT and so far all of the users we have gone back to check were on monthly. Will let you know if/when I run into a Semi-annual.

Scott

That makes more sense now, since it appears as if none were on semi-annual. Two words to pass along to your IT support person: Group Policy

In other words, s/he should be able to configure all employee computers from the comfort of their office (or cubicle), without having to walk around to each user’s computer.

I've confirmed that, after rolling back to 16.0.15726.20292, Build 2210, our quarterly reports again work just fine.

Hi,

In order to reach all those affected, I repeat my latest post from the other thread here, as otherwise you can only hope for a fix from Microsoft "by accident":

We still lack a reproduction scenario to achieve anything at Microsoft. If someone can reliably generate the problem on their end, perhaps they could do the following:

1. create a copy of the SQL Server db
2. reduce the copy to the necessary tables/views to get the error
3. anonymize data, if necessary
4. script out the resulting db
5. reduce the frontend to the necessary parts to get the error
6. make a zip file with the resulting frontend+backend available and inform us

I know this is a bit elaborate, but it's currently my only idea to get something going.

George has also updated his doc article to say that we primarily need a repro scenario.

Servus

Karl

Hi Karl, I believe I have put something together that duplicates the issue of a massive spike in memory usage which leads to the system resources or memory errors.

I need to finish scrubbing the data before sending it over.

Should I email you the zip file cotaining the front end and the scripted sql database?

Scott

Hi Scott,

If the zip file is up to a few MB you can email it. Otherwise you should load it up somewhere and send me the link and instructions via email.

Servus

Karl