The Application.Run method shown by tigravatar works dynamically (i.e., everything is allowed at runtime), and this is the easiest way to quickly call some procedure.
If you access many procedures or use more functions or subnets, you can add a link to the project name Personal.xlsb (through Tools> Links). You should rename the VBA project codename Personal.xlsb from the default "VBAProject" to something unique, such as "PersonalLibrary" or something else. Then you add a link to PersonalLibrary.
Then you get full access to all public functions and subsystems in standard modules, any sheets and classes, early binding to classes and access to fields, properties and events.
This additionally comes with the benefits of intellisense and standard compile-time tests, such as checking method signatures (that is, that the function arguments or sub match what should be) and static typing.
(note that for Classes you will need to use the function in the standard module Personal.xlsb to return an instance of any class, since they are not "creative" external projects)
In your case, you can access it by adding a link, just like PersonalLibrary.Password(target)
source share