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 No comments

97 answers

Sort by: Most helpful
  1. Anonymous
    2024-08-30T17:03:08+00:00

    Consider switching to the Semi-Accual enterprise channel and avoid bugs like this in the future, more information here:

    BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

    Juan Soto

    14x Access MVP

    AccessExperts.com

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-08-30T16:59:18+00:00

    Hi John

    Consider switching to the Semi-Accual enterprise channel, more information here:

    BUG ALERT: Access not closing on exit in build 2408 - Access developer (accessexperts.com)

    Juan Soto

    14x Access MVP

    AccessExperts.com

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-08-30T14:24:34+00:00

    I'm getting this error any several others. I'm unable to roll back to any prior version. I have to reboot my PC to end the session, then manually delete the lock file. But any time I try to execute a dynamic query using the CurrentDB.Execute command, I get the other error Run-time error '3048': Cannot open any more databases. And it starts all over again. The problem with not exiting didn't start until after the update on 8/29. The problem with the 3048 error started with the 8/29 error. So they may or may not be related. Regardless, I can't go back to a prior update so I'm dead in the water until they fix the bug.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-08-30T10:55:00+00:00

    I also had this, with the added "cannot open any more databases" error.

    I burnedback to vesrion 2407, all issues went away.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-08-30T06:48:36+00:00

    Same issue as others. "Cannot open any more databses", and Access doesn't quit properly.

    It errors at an OpenRecordSet.

    Was working before. Applied updates. Now it's not working.

    Version is: 16.0.17928.20114 32-bit

    I used this tool: Available Connections (isladogs.co.uk)

    And I can see the number available drops and doesn't come back up even after closing all the forms.

    I went through and ensured every OpenRecordSet I can find has a corresponding close and set to Nothing.

    Was this answer helpful?

    0 comments No comments