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

Hi,

Thanks for your repro steps. Unfortunately, they don't work for me.

1. I see v3.16 in both versions of Colin's tool (accdb and mdb) after the download.
2. In my M365 version 2408 17928.20114, 64-bit neither the simple repro nor the one with some thousand additional records in a linked table use up any connections. Note the different bitness.
3. The only 32 bit version I have in the moment is Access 2016 version 2408 17928.20114. Same result there.

So, I'm still not able to reproduce the problem.

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

Olá pessoal,

Estava com esse problemas a dias. Não estava entendendo pois nos meus clientes tudo estava funcionando.

Porém, quando vi comentários sobre o problema da nova versão, procurei achar soluções para o problema e me deparei com o site https://www.devhut.net/another-msaccess-exe-process-not-closing-properly-bug/ onde, não opção 2, é orientado a criar um local confiável para a pasta onde se encontra o seu ACCDB.

Fiz isso e tudo voltou a funcionar sem precisar voltar versão. Muito legal!

Tentem ai !

Abraços

Hi affected people,

The simple reproduction steps in the initial post here never have worked for me. I've also tried to get 3048 or a hanging background process with a few thousand records, with different databases, with Northwind, all without "success".

Can anyone here provide a reliable repro scenario or better yet a database where the error and/or hanging process reliably occurs?

This would be very helpful in discussions with Microsoft.

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

3048 Error Reproduction

Microsoft Access for Microsoft 365 MSO (Version 2408 Build 16.0.17928.20114) 32-bit

Simple Reproduction with database:

1. Download and open this: Available Connections (isladogs.co.uk) and notice every refresh(10 seconds by default) that 2 more connections are used up and not returned to the pool/garbage collected.

There are two calls to CurrentDB each refresh, the expectation is that the calls to CurrentDB should be auto garbage collected. They are not.

This causes the pool to empty and when you exit, the references are left open.

If you change the CurrentDB to an object and call close on it, you won't have any leaks and Access may (or may not) close properly.

----------------------- OLDER INFORMATION BELOW--------------

1. Create new database A with Table1
2. Create new database B with Table2
3. In Database A, link Table2 ( External Data -> New Data source -> From Database -> Access -> Link to the data source by creating a linked table )
4. In Database A use this: Available Connections (isladogs.co.uk) and notice every refresh(10 seconds by default) that 2 more connections are used up and not returned to the pool/garbage collected

• To make it worse, have a large table and create a continuous form that has a field that uses a function that calls CurrentDB
• This also creates the hanging background process.
• Further testing I've done shows that if you call .close after every usage of CurrentDB, it seems to properly clean up after itself and you'll get no leaks (in *your* code). But you need to manually close each usage of CurrentDB, the garbage collector doesn't seem to do it.

(Note, I don't know why the form says v3.14 at the bottom when it's in the download for 3.16 on the site)

Hi affected people,

The simple reproduction steps in the initial post here never have worked for me. I've also tried to get 3048 or a hanging background process with a few thousand records, with different databases, with Northwind, all without "success".

Can anyone here provide a reliable repro scenario or better yet a database where the error and/or hanging process reliably occurs?

This would be very helpful in discussions with Microsoft.

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

I created a function fncADO_Execute to replace the CurrentDB function. I pass it the SQL string that CurrentDB would have used. It works most of the time. Although there are a few queries that won't work using the ADO version. So, I have an On Error section that flips it back to the CurrentDB if it fails. And that also works.

I've also had some issues where executing an actual Query creates some bogus issue, including trying to tell me that my database is unknown. So, I put the SQL code into the strSql variable and call the fncADO_Execute function instead.

Public Function fncADO_Execute(strSql as String) As Boolean

    Dim bolOK As Boolean

    Dim cn As New ADODB.Connection

    Dim cmd As New ADODB.Command

    Dim prm As New ADODB.Parameter

    Dim g_Connection As String

    g_Connection = CurrentProject.Connection

    Set cn = New ADODB.Connection

    cn.Open g_Connection

    '***** Fix Error - 3048 *****

    Set cmd = New ADODB.Command

    On Error GoTo ErrorHandler     

    With cmd

        .ActiveConnection = cn

        .CommandText = strSql

        .CommandType = adCmdText

    End With

    cmd.Execute

    cn.Close

    Set cmd = Nothing

    Set cn = Nothing   

    bolOK = True

    GoTo Done                      

ErrorHandler:

    CurrentDb.Execute strSql       

    Debug.Print                    

    bolOK = True                   

Done:                              

    fncADO_Execute = bolOK

End Function