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

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

In any environment controlled by IT, simply put in a ticket to have the system downgraded and mention the known bug, crashing, hung processes, risk of corrupting data, downtime, .... they will resolve the issue with ease. I also recommend supplying a little to one of the support articles on the subject and getting your manager to also put in a request to add administrative weight to the matter so it is resolved promptly.

That said, IT, have tools to automate this with ease and considering the issue at hand they should have no issue doing so. In my experience, when properly presented IT has always helped out in resolving such matters.

unfortunately... my company IT regulation is restricting users modify the regedit

btw updating from me.. i am able to run the macros after downgrade to prev. version office

so if you all facing the issue, you can downgrade the version before 2408 and waiting update fix version.

I can't revert due to our IT policy, and making the front and back end trusted has no effect.

However, I've been able to mitigate the "Error 3048 - Cannot open any more databases" issue to a degree by rewriting the VBA code, removing every instance of call to CurrentDB and replacing it with a similar code call to the below and ensuring it's closed and set to Nothing after use. I also replaced every instance of DLookup with a call to NiceDlookup from here DLookup and “NiceDLookup” | Access JumpStart, in particular the second version by Eric Blomquist  (which actually doesn't compile and needs a little tweak).

I haven't noticed any performance regressions. It doesn't solve the .exe being left open, but at least I can use my database without it falling over itself instantly from too many open databases.

Function CurDB() As DAO.Database 

Set CurDB = Access.Application.DBEngine(0)(0) 

End Function