After updating Access in Office 365 to version 2408, the MSACCESS.EXE process remains after exiting Access.

Servus Karl,

JA, es sind noch viele schwerwiegende Bugs enthalten. Bugs, die das Laufen einer Access-App unmöglich machen.

Hatten wir auch schon vor einigen Jahren, jetzt wieder:
Unerklärliche Fehlermeldungen an diversen Stellen: "... Mehr Datenbanken können nicht geöffnet werden".
Hat nichts mit nicht geschlossenen Recordsets zu tun, meine App läuft seit 10 Jahren stabil.

In reply to the problem experienced in this thread, I too am experiencing the same problem. Running 365 in a local environment. 3048 and the lockfiles don't close on closing the database. I am running the 32 bit version of Office 365. So the problem is not confined to the 64 bit version.

To delete the lockfiles without restarting the computer: Scroll down in task manager until the MSAccess.exe is found and close the application. The lockfiles can then be deleted.

This does not solve the problem, but at least the database can be restarted and the problem reincountered.

Background information: The problem came out of the blue upon which I deinstalled and reinstalled office, to no avail. Microsoft stated that this bug had been fixed with an earlier release of 365. Evidently not!

My question: can I return to an earlier version of 365 and how to do this?

Hopefully Microsoft will come up with a solution soonest.

Thank you.

We've starting having this with several customers this week but it hasn't been consistent. I have the same version on my computer and am unable to reproduce. Could it be related to rights? Trusted?

Is there a workaround besides rolling back the update? We would have hundreds of people to adjust so it's not a great option.

Hi,

We have published a documenting article on AFo with information about the planned fix by Microsoft.

Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

MS Access 2019 Version 2408 (Build 17928.20114 Click-to-Run) not functioning properly, previous version of 2407 functioned correctly. Behavior started on 8/27/2024. I had another machine with MS Access Version 2019 and 2021 Version 2404 (Build 17531.20152 Click-to-Run) which do not experience the issues.

It does the following:

1. Opening the application with the shift key so no code executes on startup and exiting MS Access does not produce an error. Accessing only an internal Access table within the application and exiting MS Access does not produce an error.
2. Opening a linked table in MS Access results in an error.
3. Opening the application in the normal method which accesses a linked table to trigger the login screen to the external database always results in an error. There are two versions of the application. The older uses SQL Server Native Client 11.0 to SQL Server 2019. The newer version uses ODBC Driver 18 for SQL Server to Azure SQL Server.
4. The error observed is on application close the application task terminates in Task Manager and a background task starts for MS Access. The background task never terminates. Unless the background task is manually terminated, MS Access will not restart the application and no error message is thrown.
5. If the application is set to compact on close, once the application terminates, the background task attempting to compress the database throws an error that a user has already locked the application.
6. Additional observations, after opening and "saving as" several queries, MS Access will no longer save the queries and throws no error.

Running on Windows 10 Pro Version 1H1 OS build 19043.2364