Fully Qualified Procedure Names
When we call a public procedure that lies in another code module, there is a potential problem with ambiguity, for there may be more than one public procedure with the same name in another module. VBA will execute the first one it finds, and this may not be the one we had in mind!
The solution is to use a qualified procedure name, which has the form:
ModuleName.ProcedureName
For instance, if a public procedure named AddOne
lies in a module named Utilities, then we can call this procedure
using the
syntax:
Utilities.AddOne
Get Access Database Design and Programming, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
