M
Michael G. Schneider
In an Excel file two AddIns are used. These are the "Analysis Functions" and
"Analysis Functions - VBA" AddIns (maybe wrong name, translated from
German).
If the Excel file is opened by the user directly, anything works fine.
However, if the file is opened (on the same PC, by the same user) via a VB
dotnet program, the AddIns cannot be used directly. They have to be loaded
by code.
One more observation...
Suppose the VB program has started Excel and loaded the file. Now, if you
then open the menu command "Tools >> AddIns" (maybe wrong name, translated
from German), the two AddIns are selected. You have to remove those
selections, close the dialog, open the dialog again, and set the selections.
Only then the AddIns can be used.
However, there are also situations where an Excel file is opened from a VB
program and the AddIns are available immediately. I do not see any clue, why
this works sometimes but not all the times.
Michael G. Schneider
"Analysis Functions - VBA" AddIns (maybe wrong name, translated from
German).
If the Excel file is opened by the user directly, anything works fine.
However, if the file is opened (on the same PC, by the same user) via a VB
dotnet program, the AddIns cannot be used directly. They have to be loaded
by code.
One more observation...
Suppose the VB program has started Excel and loaded the file. Now, if you
then open the menu command "Tools >> AddIns" (maybe wrong name, translated
from German), the two AddIns are selected. You have to remove those
selections, close the dialog, open the dialog again, and set the selections.
Only then the AddIns can be used.
However, there are also situations where an Excel file is opened from a VB
program and the AddIns are available immediately. I do not see any clue, why
this works sometimes but not all the times.
Michael G. Schneider