What it does
Core purpose
You can also check out [Greedo's code review](https://codereview.stackexchange.com/questions/274532/low-level-vba-hacking-making-private-functions-public).
Where it sits
Calling private module functions belongs to the Low level tools family of VBA community tools. It is listed on the community-maintained awesome-vba index and is actively used by Microsoft Office automation developers.
How to get it
Source location
Full source, documentation, and release notes are maintained at github.com. Treat that URL as the canonical reference — bugs and feature requests live there.
Installation pattern
For a typical GitHub-hosted VBA library: download the .bas, .cls, or .frm files from the repository, then in the VBA editor (Alt + F11) use File → Import File… to bring each module into your project. Save the host document as .xlsm, .accdb, or .docm so macros are retained.
When to use it
Best fit
Reach for Calling private module functions when your automation needs Low level tools capability and you want a peer-reviewed library rather than rolling your own. The awesome-vba curator reviews inclusions for active maintenance and community support.
Alternatives worth evaluating
Before committing to Calling private module functions, browse the other entries in the same Low level tools section of our tools directory — several libraries typically overlap in purpose, and the right pick depends on your Office version, 32- vs 64-bit target, and licensing needs.