[German]A blog reader has just contacted me because he has run into significant problems with Microsoft Access with Microsoft Office 365 version 2408 (Build 17928.20114). He often gets error 3048 from the Access frontend when trying to access it. The question is whether other users are also experiencing this.
Microsoft Office 365 Version 2408 (Build 17928.20114)
I just checked the Office 365 update history, Microsoft Office 365 version 2408 (Build 17928.20114) was not released in the Current Channel until August 26, 2024.
There are database problems
Rudolf has just contacted me on Facebook in a private message and asked me if I had already received any problems from readers about the new Office build. I had to say no. Rudolf wrote:
Hello Günter,
Have you already been asked if there are any problems with Access Frontend (SQL databases?) with the current Office version?
Error 3048 appears very quickly and very often in Access ("No further database connections possible").
I later got a 2nd confirmation from a reader. For error code 3048 in Access there was already this Techcommunity post in 2022 and a support article Access is unable to close and leaves lockfile active. However, this referred to a different build and the problem should have been fixed long ago.
Rudolf wrote that he even reworked his entire Access code to ensure that objects and recordsets are deleted and separated. But that didn't help. In the end, he downgraded from the problematic version 2408 (build 17928.20114) to the latest version. After that, everything works again.
The interesting question now is whether anyone from the readership has also made these observations? If so, are there any specific findings or another workaround, apart from "going back to the last Office 365 version"?
Addendum: There is now a huge discussion After updating Access in Office 365 to version 2408, the MSACCESS.EXE process remains after exiting Access in Microsoft Answers community. The AFo-Team has published an article with information about Microsoft's plan to ship a fix.
MS Access Error 3048: On 2 Sep24 I also started having the same problem on version 2408 build 17928.20114 and when opening with another version 2407 build 17830.20166I do not have the same problem. I have a split Db with backend on a NAS. due to the fact that it works and doesnt on different pc I conclude it is the version. I also changed my maxlocksperfile in the registry to 200000 but seems to help slightly.
Some problem started here on September 1st. When you open a recordset in VBA (like : Set dbs = CurrentDb // Set rst = dbs.OpenRecordset("TableName") // rst.Close // Set rst = Nothing // dbs.Close // Set dbs = Nothing). This will not work and leave dbs open. If this is part of an iteration, error 3048 will occor.
If you open the rst in VBA just one time and close the Access application, it will leave the lockfile open. The workaround I use : after closing the Access application, open the Task Manager and also close Access there.