MS Access RunCode Macro cannot find my procedure

calendar_today Asked Jun 21, 2013
thumb_up 15 upvotes
history Updated April 14, 2026

Direct Answer

THEN I read the error message carefully. It mentions that it could not find the FUNCTION name. Apparently, the RunCode property specifically requires a "Function" not a Sub. So, I…. This is a prose walkthrough, ranked #15th of 67 by community upvote score, from 2013.


The Problem (Q-score 7, ranked #15th of 67 in the Access VBA archive)

The scenario as originally posted in 2013

I’m only posting this since I wasn’t able to find a solution anywhere. I finally figured it out. Kind of silly really.

When using the RunCode property within an Access Macro, I was trying to run a Sub from my global module. I was getting the error “The expression you entered has a function name that database can’t find.” I couldn’t figure out what the issue was. I followed the advice of everyone that posted on this issue, which was mostly the following:

  1. Use () at the end of the procedure name
  2. DO NOT use the “=” before the procedure name

Still didn’t work!

Why community consensus is tight on this one

Across 67 Access VBA entries in the archive, the accepted answer here holds strong answer (top 25 %%) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — strong answer (top 25 %%) (+15)

Verbal answer — walkthrough without a code block

Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Access VBA entries ranked in the top 10 of the same archive.

THEN I read the error message carefully. It mentions that it could not find the FUNCTION name. Apparently, the RunCode property specifically requires a “Function” not a Sub. So, I simply changed my Sub to Function and it worked fine!

Hope this helps.


When to Use It — classic (2013–2016)

Ranked #15th in its category — specialized fit

This pattern sits in the 52% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.

What changed between 2013 and 2026

The answer is 13 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Why does this sit in the top quartile of Access VBA answers?
expand_more

Answer score +15 vs the Access VBA archive median ~5; this entry is strong. The score plus 7 supporting upvotes on the question itself (+7) means the asker and 14 subsequent voters all validated the approach.

The answer has no code block — how do I turn it into a snippet?
expand_more

Use the walkthrough above as a checklist, then open a top-10 Access VBA archive entry for a concrete starting template you can adapt.

Published around 2013 — what’s changed since?
expand_more

Published 2013, which is 13 year(s) before today’s Office 2026 build. The Access VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Access VBA pattern ranks just above this one at #14?
expand_more

The pattern one rank above is “Managing and debugging SQL queries in MS Access”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 7, Answer-score 15, original post 2013, ranked #15th of 67 in the Access VBA archive. Last regenerated April 14, 2026.

access-vba