C
Chuckles123
Charles,
Thank you!
Why do you recommend not to store .xla files in the Microsoft AddIns
folder?
Thanks for the recommendation about the AddIn Loader software; I will
check with our network people.
I have had some success with Custom Buttons accessing the macros stored
in an .XLS file on our shared drive (I know this because, when the macro
security window (Disable - Enable choice) pops up, it displays the path
of the macro source. Curiously, when clicking-on Tools>>AddIns, there
is a check-mark next to the appropriate addin, and then, when clicking
on Browse, the path is to the addin stored in the Microsoft AddIns
folder on my C drive. This latter situation is due to 2 lines of code
I keyed in at the top of the primary macro (essentially, it places a
check-mark next to the appropriate addin on the Tools>>AddIns menu).
<<== weird combination, but it works. The next test is to see if it
works for other users on our network. When I find out, I will post
this thread.
Regards,
Chuckles123
Thank you!
Why do you recommend not to store .xla files in the Microsoft AddIns
folder?
Thanks for the recommendation about the AddIn Loader software; I will
check with our network people.
I have had some success with Custom Buttons accessing the macros stored
in an .XLS file on our shared drive (I know this because, when the macro
security window (Disable - Enable choice) pops up, it displays the path
of the macro source. Curiously, when clicking-on Tools>>AddIns, there
is a check-mark next to the appropriate addin, and then, when clicking
on Browse, the path is to the addin stored in the Microsoft AddIns
folder on my C drive. This latter situation is due to 2 lines of code
I keyed in at the top of the primary macro (essentially, it places a
check-mark next to the appropriate addin on the Tools>>AddIns menu).
<<== weird combination, but it works. The next test is to see if it
works for other users on our network. When I find out, I will post
this thread.
Regards,
Chuckles123