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: Create a form named Form1. On Form1, create a command button named Command1. 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.

Hi Kal, I have just re-rolled forward to 2408 to create you a test scenario. Microsoft® Access® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 32-bit If you run the ReproduceError() function on an affected system then it will output as follows : "Open Databases : 1" "Open Databases : 2" "Open Databases : 3" etc. When it reaches 504 it is game over. On an un-affected system Microsoft® Access® for Microsoft 365 MSO (Version 2406 Build 16.0.17726.20078) 32-bit it will output "Open Databases : 1" "Open Databases : 1" "Open Databases : 1" 5000 times, as it should. Function OpenDatabaseCount() Dim td As TableDef For Each td In CurrentDb.TableDefs 'Do nothing Next OpenDatabaseCount = DAO.Workspaces(0).Databases.Count End Function Function ReproduceError() Dim i For i = 1 To 5000 Debug.Print "Open Databases : " & OpenDatabaseCount Next End Function

Hi, Thank you for your efforts, but I think I (or my environments) are just not authorised/eligible for the bug. ;-) In both Access versions that I mentioned I get Open Databases : 2 No problem with 3048, no problem with a hanging process. Servus Karl **************** Access Forever, News , DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

You must be immune. I made a mistake in my write up there, the correct response should be Open Databases : 2. The affected version will increase and increase until it explodes. At least there is an acid test now that can be done reliably.

Hi, I have just updated the status section in our documenting article . The bad news is that the fix in the Current Channel is to be expected only next week. The good news is that it has been available in the Current Channel Preview (CCP) since yesterday. That is the (beta) channel for which it was first mentioned in the initial posting of this thread and elsewhere. See the AFo article for details. As written there, fix reports from CCP are welcome. Servus Karl **************** Access Forever, News , DevCon Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

Hi Karl, I have just updated to the new version mentioned in your post (Currently in Preview). Now using : Microsoft® Access® for Microsoft 365 MSO (Version 2409 Build 16.0.18025.20024) 32-bit I can confirm that the bug appears to be fixed. It passes the test above ! And I have briefly tested several client databases - which were previously affected - but now appear to running fine. I'll continue to use it until it hit's the Current Channel next week. Thank you ! Ben

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

Anonymous

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:

Create a form named Form1.
On Form1, create a command button named Command1.
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.

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

Anonymous

2024-09-04T08:38:18+00:00
Hi Kal,

I have just re-rolled forward to 2408 to create you a test scenario. Microsoft® Access® for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 32-bit

If you run the ReproduceError() function on an affected system then it will output as follows : "Open Databases : 1" "Open Databases : 2" "Open Databases : 3" etc. When it reaches 504 it is game over.

On an un-affected system

Microsoft® Access® for Microsoft 365 MSO (Version 2406 Build 16.0.17726.20078) 32-bit

it will output "Open Databases : 1" "Open Databases : 1" "Open Databases : 1" 5000 times, as it should.

Function OpenDatabaseCount() Dim td As TableDef
For Each td In CurrentDb.TableDefs
```
    'Do nothing
Next
OpenDatabaseCount = DAO.Workspaces(0).Databases.Count
```
End Function

Function ReproduceError() Dim i For i = 1 To 5000
```
Debug.Print "Open Databases : " & OpenDatabaseCount
```
Next End Function
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T08:55:29+00:00

Hi,

Thank you for your efforts, but I think I (or my environments) are just not authorised/eligible for the bug. ;-)

In both Access versions that I mentioned I get

Open Databases : 2

No problem with 3048, no problem with a hanging process.

Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-04T09:18:45+00:00

You must be immune. I made a mistake in my write up there, the correct response should be Open Databases : 2. The affected version will increase and increase until it explodes. At least there is an acid test now that can be done reliably.
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-04T09:31:54+00:00

Hi,

I have just updated the status section in our documenting article.

The bad news is that the fix in the Current Channel is to be expected only next week.

The good news is that it has been available in the Current Channel Preview (CCP) since yesterday. That is the (beta) channel for which it was first mentioned in the initial posting of this thread and elsewhere.

See the AFo article for details. As written there, fix reports from CCP are welcome.

Servus
Karl
****************
Access Forever, News, DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg
Was this answer helpful?

4 people found this answer helpful.

0 comments No comments
Anonymous

2024-09-04T10:10:52+00:00

Hi Karl,

I have just updated to the new version mentioned in your post (Currently in Preview).

Now using : Microsoft® Access® for Microsoft 365 MSO (Version 2409 Build 16.0.18025.20024) 32-bit

I can confirm that the bug appears to be fixed. It passes the test above ! And I have briefly tested several client databases - which were previously affected - but now appear to running fine.

I'll continue to use it until it hit's the Current Channel next week.

Thank you !

Ben
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments