Application.Run Macro Works Fine For Me, Not For Another

[EnergyHOU]

Tricky situation here that I can't quite seem to understand. Note below code.

Please Login or Register  to view this content.

In short, this subroutine opens an external file, and then executes another module within the original host file that will perform work on the external file. I run it, no issue, everything executes without issue. A colleague runs it, and although it is able to get through opening the external file, a notice comes up about 'a path' cannot be found. Check your spelling, or try a different path. Upon hitting debug it highlights the:

Please Login or Register  to view this content.

line. My immediate reaction was to check if the GS_Recalc_Refresh_Print macro was local or something but quickly remembered that it's merely another module within the original host file, so why would it even need to look?

[xlnitwit]

Hi,

Are you saying that the two routines GS_Recalc_Refresh_Print and SlaveRoutineGS are located within the same workbook? If so, why do you need to use Run at all rather than calling the second routine directly?