christian.dheureuse
New member
- Local time
- Today, 12:42
- Joined
- Sep 2, 2025
- Messages
- 2
I have the same problem on several computers with Win11 and KB5064081. Different Access versions, but only 32-bit Access/Office.
My workarounds found until now (while still using ADO):
empty.mdb is a newly created empty database.
In this example, the error occurs when the VBA code calls Connection.Execute().
I tried other variants to open the recordset, other SQL statements, etc. all without success.
I also tried to install the Microsoft Access Database Engine 2016 Redistributable, but that didn't replace msjtes40.dll.
I reported the error via the Feedback Hub: aka.ms/AAxs979
Please upvote there.
My workarounds found until now (while still using ADO):
- Use ACE provider "Microsoft.ACE.OLEDB.12.0" instead of "Microsoft.Jet.OLEDB.4.0"
- Uninstall KB5064081
Code:
Public Sub test1()
Dim FileName: FileName = CurrentProject.Path + "\empty.mdb"
Dim conn As ADODB.Connection
Set conn = New ADODB.Connection
conn.Provider = "Microsoft.Jet.OLEDB.4.0"
conn.Properties("Data Source") = FileName
conn.Open
Const sql = "select 1 as v1"
Dim rs As ADODB.Recordset
Set rs = conn.Execute(sql, , adCmdText)
MsgBox "Value=" & rs!v1.Value
End Sub
empty.mdb is a newly created empty database.
In this example, the error occurs when the VBA code calls Connection.Execute().
I tried other variants to open the recordset, other SQL statements, etc. all without success.
I also tried to install the Microsoft Access Database Engine 2016 Redistributable, but that didn't replace msjtes40.dll.
I reported the error via the Feedback Hub: aka.ms/AAxs979
Please upvote there.
Last edited: