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

Anonymous
2024-08-20T05:08:41+00:00

After applying the quality update for the latest channel (preview version) of Microsoft Access (64-bit), version 2408 (build 17928.20066) dated 8/14, the MSACCESS.EXE process won't end even after closing Microsoft Access application.

The reproduction steps are as follows:

  1. Create a form named Form1.
  2. On Form1, create a command button named Command1.
  3. In the Click event of Command1, write "Application.Quit".

Run the application, click Command1 on Form1 to close the application. Afterward, when you check the Task Manager, MSACCESS.EXE process won't end.

This issue does not occur in the 32-bit version. I believe this is a bug. Can you advise where I should report this?

Rolling back to version 2407 resolved this issue.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

97 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-09-01T19:23:33+00:00

    I can't go back to a prior version. I can use Task Manager to end Access then manually delete the lock file. But that doesn't solve the other issues including the ERROR - 3408. I'm also unable to run the function to repair and compress the database. So it's just getting larger and larger every time I try to test code arounds. The locking issue is creating as many issues as ERROR - 3408. When are they going to fix this issue?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-01T19:39:05+00:00

    Kathleen,

    you can go back to an earlier version of Office.

    Search the net for "How to revert to an earlier version of Office" and you should encounter a detailed procedure to return office to a previous version. I carried out this process on my version (365) and it worked. My database works smoothly without errors.

    Best of luck.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-09-01T19:42:19+00:00

    Kathleen,

    PS: Have a look also at Karl Donaubauer's reply on the 01.09.24 just above. He included a link.

    Was this answer helpful?

    0 comments
  4. Günter Born 49,461 Reputation points
    2024-09-02T14:22:35+00:00

    @Karl: I've described some details at Office 365 Version 2408: Issues with Access when accessing a SQL database - I got several reports from blog readers (German, English).

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-09-02T14:52:34+00:00

    Hi Günter,

    Yes, a SQL Server backend is not necessary but may help to get the error symptoms. ;-) We have dozens of discussions on various forums about this, especially since the issue hit the Current Channel last week.

    I hope the (Office wide) bugfix Microsoft has planned for the next few days will really help. We will see.

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

    Was this answer helpful?

    0 comments