Office Apps Crashing

Fix Acecore.dll Crash When Opening a Microsoft Access Recordset

Steve KSteve K Oct 28, 2026 869 views

Question details

Microsoft Access crashes with an Acecore.dll error when attempting to open an ADO recordset.

How to Diagnose Acecore.dll Crashes When Opening an Access Recordset
Product
Microsoft Access
Device & OS
not provided
Scenario
A user or developer is using ADO to open a recordset via VBA or an external connection string in Microsoft Access.
Observed behavior
The application crashes unexpectedly throwing an Acecore.dll error. The generated crash dump file alone is insufficient to identify the root cause of the failure.
Before you start

Ensure you have administrative access to your database environment and locate your VBA script editor. Make a backup copy of your Access database before attempting to debug the code or run diagnostic tools.

Solution 1Recommended

Gather Comprehensive Diagnostic Information

Since a crash dump is not sufficient on its own, you must collect specific code and environment details to identify the root cause of the ADO recordset failure.

The Acecore.dll file processes core database engine tasks. When it crashes during a recordset operation, the fault usually lies within the query syntax, connection parameters, or the data provider, rather than the DLL file itself.

1
Extract the recordset-opening code

Open the VBA Editor (ALT + F11) in Microsoft Access and copy the exact VBA snippet used to open the ADO recordset.

2
Document the connection and SQL details

Locate the connection string and the specific SQL query being executed. Ensure you note the OLEDB provider version being referenced.

3
Identify software versions

Click on 'File' > 'Account' > 'About Access' to note your exact Microsoft Access version, and press Win + R, type 'winver' to get your exact Windows version.

4
Record on-screen errors

Trigger the crash again and write down any specific on-screen error messages or warning codes leading up to the unexpected closure.

Gather Comprehensive Diagnostic Information
Analyzing the Data: Providing these specific details to Microsoft Support or IT forums will help pinpoint whether the issue is with the SQL query, the database provider, the underlying data, or the Access installation itself.
Free Microsoft Office alternative

Experience Unmatched Stability with WPS Office

While WPS Office does not include a direct database building tool like MS Access, it is the perfect companion suite for your daily document workflows. Replace unstable word processors and spreadsheet apps with a highly stable, free, and lightweight suite that handles your everyday office tasks seamlessly.

  1. 1. Visit the official WPS website: Go to the official WPS Office website using your web browser.
  2. 2. Download the installer: Click the 'Free Download' button to get the lightweight installation file for your operating system.
  3. 3. Install and launch: Run the downloaded file, follow the quick setup wizard, and start enjoying a stable, crash-free office experience.
Fully compatible with Microsoft Word, Excel, and PowerPoint formats (.docx, .xlsx, .pptx).Lightweight installation that prevents the system crashes and DLL errors common in heavy office suites.Completely free to use with a familiar, easy-to-navigate user interface.Built-in PDF editor lets you manage all your document workflows in one unified, tabbed window.
microsoft office alternative - wps office

Frequently Asked Questions

What is Acecore.dll in Microsoft Access?

Acecore.dll is a core dynamic link library file used by the Microsoft Access Database Engine (ACE). It is responsible for processing queries, handling database connections, and managing memory allocation during data operations.

Why does opening an ADO recordset cause Access to crash?

This crash typically occurs due to malformed SQL syntax, incompatible OLEDB providers, corrupted database records, or a damaged Acecore.dll file within the Office installation directory.

Why is a crash dump file not enough to fix an Access crash?

A crash dump file only reveals the final point of failure (e.g., inside Acecore.dll). It does not capture the faulty VBA code, the exact connection string, or the specific SQL query that triggered the failure, which are essential for resolving ADO issues.