A
aaronfude
Hi,
This is basically a follow up question to Charles Williams.
Charles, you posted this very nice code to help my VBA addin assure
that the C# addin that it depends on is loaded first.
dim oAddin as addin
on error resume next
set oaddin=nothing
set oaddin=addins("MyProjectname.classname")
on error goto 0
if oaddin is nothing then
addins.add("MyProjectname.classname")
set oaddin=addins("MyProjectname.classname")
endif
if not oaddin.installed then oaddin.installed=true
And, in fact, the desired effect takes place if the C# addin is not
installed. But - the weirdest thing!!! - if I had previously quit Excel
with the automation addin "clicked in", then this code does not
accomplish its mission and the functions stored in the automation addin
are not available to the VBA add-in!
Any ideas on what might be going wrong?
Grateful,
Aaron Fude.
This is basically a follow up question to Charles Williams.
Charles, you posted this very nice code to help my VBA addin assure
that the C# addin that it depends on is loaded first.
dim oAddin as addin
on error resume next
set oaddin=nothing
set oaddin=addins("MyProjectname.classname")
on error goto 0
if oaddin is nothing then
addins.add("MyProjectname.classname")
set oaddin=addins("MyProjectname.classname")
endif
if not oaddin.installed then oaddin.installed=true
And, in fact, the desired effect takes place if the C# addin is not
installed. But - the weirdest thing!!! - if I had previously quit Excel
with the automation addin "clicked in", then this code does not
accomplish its mission and the functions stored in the automation addin
are not available to the VBA add-in!
Any ideas on what might be going wrong?
Grateful,
Aaron Fude.