MS Access Memory Issue

Question

Programming in Access 365 but it is a 32-bit access front end with a SQL Express backend. Been using this database for years with no issues. All of a sudden starting approx. last Monday 12/12/2022 we started getting out of memory errors on the client side. Users started getting it randomly over 2 or 3 days as if it was an update.

If I open the database and watch task manager, as I open forms and close them, I see the memory usage go up when the form is opened as expected but it never goes back down to where it started from when the form is closed. We have a few form timers that run code every 2 to 5 minutes and the same thing happens, memory usage goes up when the timer triggers but when the code finishes the memory is not released.

I have run CHECKDB on the SQL Express tables, I have also run a SQL Shrink Database. On the front end, I have decompiled the database, run a compact and repair and then recompiled it.

I have been able to reproduce the issue on a computer at my house with a different access database. This database is a 64-bit database with access tables not SQL. The same thing happens, when I open forms then close them the memory usage does not return to the amount before the form was open, always just a little higher until I get the error message.

Answer 1

The computer running 64 bit Access that I was able to recreate the issue on is a custom built pc running Windows 11 (Specs below).

What about making sure you are properly closing any DAO recordsets? You could have been dangerously close to “tipping the apple cart” before (without knowing it), and the latest update was enough to push you over the finish line so-to-speak.

Current channel or semi-annual update for Office? I believe Current channel is the default, but semi-annual seems to be a lot more reliable.

Answer 2

On the 64 bit access computer, definitely not. It is an access frontend and backend all in one database and all record sets are opened by the query feeding the form. No manual DAO calls.

On the 32-bit version it is possible there are some that could be left open, but we try to make sure we close every DAO when we are done with it.

Answer 3

Mike, if you have task manager open next to the program do you see the memory usage increase with each function you run and really doesn't release it after done? That's what I'm see across a couple of my applications. I've been looking for a cause but have had no luck. Recordsets are closed, CurrentDB, etc. We are in the process of creating 64 bit versions but are not ready for wide release yet. Not encouraging if you are having the same issue in 64 bit.

Also hearing that semi-annual should be coming out in the next week or so which is going to hit my customers again as we have been rolling back updates to semi-annual.

Keep me posted and I'll do the same.

Answer 4

That is exactly what is happening. My major issue is in 32 bit, that's our production database. The 64 bit was just testing to see if I could recreate the issue on another computer, which I did.

Answer 5

Going to 64 bit is a tough one for us but at least we thought it was a possible solution. At this point I can't pinpoint what is causing it.

Is your backend SQL or Access database?

This is our only option for reaching out to Microsoft support correct?