Reported issues for Microsoft Access Database
Pod holds 18 of 20 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to Microsoft Access Database.
Most discussed
Option to open the database exclusively (Feature request)
What. A way to make the server's implicit OpenCurrentDatabase call pass Exclusive:=True.
Why. When the server drives a build that changes table design — attaching Data Macros via SaveAsText/LoadFromText, or anything going through DoCmd.OpenTable acViewDesign — a table that another Access session has open cannot take a design lock. The operation fails for that table only, and the failure is easy to miss: a run can complete, report success, and have changed nothing. Opening exclusively turns that
Read the thread · 2026-08-27 · open · external user · 4 comments
Ghosting Combo boxes when toggling visibility of form recordselectors
I am forwarding this bug report which I submitted to Microsoft on to you ONLY because I had Claude Code create the form from scratch using JuanJo Luna's implementation of your MCP-Server for Access. The form was 100% the result of that. I only tested the result. Totally awesome.
I do not know one way or the other is there is any relevance, but in the interest of completeness, I thought I would include you in the reporting loop in case there actually is some sort of connection.
Read the thread · 2026-05-12 · closed · external user · 5 comments
Second instance of Access is being created.
Here is a fragment of CC explaining why sometimes a second instance is being created, while we would want to continue with the first instance. I downloaded this version of the MCP just yesterday.
You called access, but it was already open, so a second instance opened. That usually does not end well. How can we avoid that?
● This is a limitation of how the MCP Access tool connects. Based on the stack trace I saw earlier, it uses _switch(resolved) in core.py — likely calling CreateObject("Ac
Read the thread · 2026-04-14 · closed · external user · 2 comments
_get_vb_project causes error
This is the first time I have Claude Code = CC look at this accdb, and this error was the result. I had just downloaded and unzipped your latest MCP.
access - access_list_objects (MCP)(db_path: "D:\M2Dev\Claude\Projects\Anonymize\Anonymize_Claude.accdb", object_type: "all") ⎿ Error: cannot import name '_get_vb_project' from 'mcp_access.core' (D:\M2Dev\Claude\MCP\MCP-Access-main\mcp_access\core.py)
Read the thread · 2026-04-07 · closed · external user · 1 comment
access_vbe_append 'new_code' is a required property
access - access_vbe_append (MCP)(db_path: "D:\M2Dev\Claude\Projects\AbbottGranite-AGI2\AGI2_DEV.ACCDB", object_type: "module", object_name: "modScheduleForm", code: "---code omitted---" ⎿ Error: Input validation error: 'new_code' is a required property
Is there ambiguity about "code" versus "new_code"?
Read the thread · 2026-03-29 · closed · external user · 2 comments
access_run_vba flaky in some cases only - invalid reference to property Visible
access - access_run_vba (MCP)(db_path: "D:\M2Dev\Claude\Projects\AbbottGranite-AGI2\AGI2_DEV.ACCDB", procedure: "modScheduleForm.testTrace", timeout: "60") ⎿ ERROR in tool 'access_run_vba' Type: com_error Message: (-2147352567, 'Exception occurred.', (0, None, 'You entered an expression that has an invalid reference to the property Visible.', 'dao360.chm', 2015567, -2146825833), None)
Arguments received:
{
"db_path": "D:\\M
Read the thread · 2026-03-29 · closed · external user · 2 comments
Input validation error occurred in access_vbe_get_lines
Using Northwind Developer Edition, I asked for a detailed explanation of HighlightControl, and as part of that I got this error:
access - access_vbe_get_lines (MCP)(db_path: "D:\M2Dev\Claude\Projects\NW2-Dev\NW25-Dev.accdb", object_type: "module", object_name: "modValidation", start_line: "1", count: "10") ⎿ Error: Input validation error: '1' is not of type 'integer'
Read the thread · 2026-03-26 · closed · external user · 2 comments
Exception occurred in tool 'access_vbe_search_all'
I am using Claude Code (CC) for the first time, and your MCP server. So far working quite well. As a test project I am using the Northwind Developer edition template (I am one of its authors).
This is my prompt in CC:
Explain in detail how HighlightControl works.
● access - access_vbe_search_all (MCP)(db_path: "D:\M2Dev\Claude\Projects\NW2-Dev\NW25-Dev.accdb", search_text: "HighlightControl") ⎿ ERROR in tool 'access_vbe_search_all' Type: com
Read the thread · 2026-03-26 · closed · external user · 1 comment
Most recent
VBE-write tools surface an Access DoCmd.Save error dialog (no watchdog on the write path)
Bug: VBE-write tools surface an Access DoCmd.Save error dialog (no watchdog on the write path)
Env: latest build; Access attached instance, .accdb with the target module/form open in the VBE.
Symptom: Each access_vbe_replace_lines / access_vbe_replace_proc call pops a DoCmd error dialog in the Access UI — one per write call (3 edits → 3 dialogs). The tool itself still returns "OK" and the edit lands.
Root cause: the "Persist VBE changes to .accdb" step in the write functions —
mc
Read the thread · 2026-06-25 · closed · external user · 1 comment
Duplicate "design" key in tips.py silently shadows the VBE/encoding tip
mcp_access/tips.py defines the key "design" twice in the same _TIPS dict literal:
- First occurrence (before
"macros"):"design": ( "Design view + VBE conflict:\n" " After design operations, the form may remain open in Design view.\n" " access_vbe_replace_proc closes the form (acSaveYes) before accessing VBE.\n" " All design operations invalidate the cache pair (_parsed_controls_cache, _cm_cache).\n\n" "SaveAsText encoding:\n"
Read the thread · 2026-06-21 · closed · external user · 1 comment
attached mode: modal dialogs hang eval/delete calls indefinitely; eval lacks dialog watchdog; stale _mcp_eval_wrapper wedges session
Problem
In attached mode (session acquired via GetActiveObject because the user has Access open), any Access/VBE modal dialog raised during a blocking COM call hangs the tool call indefinitely, with zero feedback. Two real incidents from one working session (2026-06-11, Access 16.0 / Microsoft 365):
Incident A — VBE compile-error modal vs access_eval_vba.
An eval'd function lived in a module with a (deliberate, freshly introduced) compile error — a local variable shadowing a
Read the thread · 2026-06-12 · closed · external user · 1 comment
access_vbe_get_proc returns stale data
CC had a really hard time updating a SQL statement in a VBA proc. It turns out it was off by a line number, and the access_vbe_get_proc returned what appears to be cached data, rather than the actual program text. Note the doubling up of "THEN 1 ELSE 0 END" in the return of that call, while this was not in the program text (also below).
Hmm, did we discover another bug in MCP? What tool were you using to retrieve the proc text?
Read the thread · 2026-04-24 · closed · external user · 1 comment
compile_vba causes a second instance of Access
During this repro, keep Task Manager open on the side, Details tab, filtered for "msaccess". Open Access. Load your test db. Observe TM is showing 1 instance of msacces. Verify the code is fully compiled. Ask CC to compile the app. Observe Access flickering, and at the end we have 2 instances of msaccess. CC reports a clean compile, but this is not good.
Read the thread · 2026-04-18 · closed · external user · 1 comment
access_set_code cannot create a class module
This creates a Standard Module, but the intent was to create a Class Module. CC says: From the tool's schema, object_type only accepts: module, form, report, query, macro. Your friend would need to add a class_module type (or a flag like is_class) to support creating class modules properly.
● access - access_set_code (MCP)(db_path: "D:\M2Dev\Claude\Projects\Anonymize\Anonymize_Claude.accdb", object_type: "module", object_name: "clsLog", code: "Option Com
Read the thread · 2026-04-07 · closed · external user · 1 comment
access_vbe_append fails with "Catastrophic failure" when Trust Center programmatic VBE access is disabled
Description
access_vbe_append (and other VBE COM tools) fail with a cryptic (-2147418113, 'Catastrophic failure', None, None) error when the Access
Trust Center setting "Trust access to the VBA project object model" is disabled. Indeed, they sometimes error even when the setting is enabled. (I.E., this broke without my changing that setting.)
access_vbe_patch_proc uses a different internal mechanism and continues to work in the same situation, so the failure is specific to the CO
Read the thread · 2026-04-05 · closed · external user · 1 comment
access_get_form_property error: object_type is required
Similar perhaps to the previous issue.
access - access_get_form_property (MCP)(db_path: "D:\M2Dev\Claude\Projects\AbbottGranite-AGI2\AGI2_DEV.ACCDB", object_name: "srptSchedules_T", property_name: "OrderBy") ⎿ Error: Input validation error: 'object_type' is a required property
Read the thread · 2026-03-29 · closed · external user · 1 comment
access_vbe_find: bug in MCP or in Claude?
● Let me search for where YYYYWW is used in the report code.
● access - access_vbe_find (MCP)(db_path: "D:\M2Dev\Claude\Projects\AbbottGranite-AGI2\AGI2_DEV.ACCDB", search_text: "YYYYWW", object_type: "report") ⎿ Error: Input validation error: 'object_name' is a required property
Read the thread · 2026-03-29 · closed · external user · 1 comment
access_eval_vba: cannot find the name of a fully qualified property
NOTE: clsErrorHandler is a "default instance" class. TraceFilePath is a Property Get.
access - access_eval_vba (MCP)(db_path: "D:\M2Dev\Claude\Projects\AbbottGranite-AGI2\AGI2_DEV.ACCDB", expression: "clsErrorHandler.TraceFilePath") ⎿ ERROR in tool 'access_eval_vba' Type: RuntimeError Message: Error evaluating 'clsErrorHandler.TraceFilePath': (-2147352567, 'Exception occurred.', (0, None, "AGI-SQL Server Edition - DEV - v.2.3108 cannot fin
Read the thread · 2026-03-29 · closed · external user · 1 comment
The remaining reports are on the project's issue tracker.