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-08-30T18:19:02+00:00

    No, I use the 32bit version and have most of the symptoms described above, including yours.

    Mine does not run out of databases immediately, though. It takes a while with lots of SQL queries going to a linked ODBC database before it starts to complain.

    Another issue I get often is an error when I close down Access. The error states that:

    You attempted to open a database that is already open by user 'Admin' on machine 'nnn'.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-08-30T19:09:51+00:00

    My data base has had quite a few problems with the latest MS Office Version. Tables not being able to be written to due to open already when they are not. Closing the data base I get error that I'm trying to open the data base that's already open. The shift key plus open does not work. Sometimes it will not open at all. until I go in the Task Manager and close all processes still running. I cannot roll back here so I am stuck until MS fixes the bug!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-08-30T23:21:17+00:00

    One more issue I have noticed with 2408 (and possibly 2407)... When I make an .accde from my .accdb, the 'save as' dialog will open to 'My Documents' no matter what. Previously, it would open to the location of the .accdb which is exactly what I needed. With 2408, I have to navigate every time to the proper location before saving, or save and move the .accde after the save.

    I reverted to 2406 and now when creating .accde the 'save as' opens to the parent .accdb location again. Hoping that 2408 will be fixed so that it will behave this way in the future.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-31T11:33:02+00:00

    You don't have to completely logoff to be able to delete the .laccdb file. If you end the main Microsoft Access task from the Task Manager, you can then delete the .laccdb file without logging all of the way out. Its a small thing but it will prevent you from logging off and closing down all of your applications

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-08-31T13:44:05+00:00

    Thanks, but I've already used task manager to end the process and manually delete the file. That closes the database. But it still doesn't fix the other error which caused the lock in the first place. I hope that Microsoft fixes this issue soon. Because I cannot roll back to a prior version as suggested by others. And I'm already past my deadline for the reports generated by the broken database.

    Was this answer helpful?

    0 comments