Word addin not loaded when application is started with VBA from within Excel

Anonymous
2019-05-17T11:20:39+00:00

I have an add-in (dotm template) which is stored in Word's Startup folder. Among other things it contains a customized ribbon.

This works fine, no problems when Word is started from the menu, double clicking a document etc. The add-in is loaded and the customizations in the ribbon are visible.

However if Word is started from VBA within another application (Excel or Access) the customizations in the ribbon do not show. If I check in the Developer tab the Add-in is listed and is selected as well.

Even if I unselected it (unload) and select (load) it again from the interface, the customized ribbon does not show.

This worked fine in Office 2010 with the exact same Excel VBA code and the same add-in.

Why does it not work in Office 2016? 

Version 1904

Build 11601.20178

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

42 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Doug Robbins - MVP - Office Apps and Services 323.6K Reputation points MVP Volunteer Moderator
    2019-05-18T04:06:57+00:00

    Setting a reference to the Microsoft Word 16.0 Object Library makes no difference here when using a 32-bit installation of Word Version 1904 (Build 11601.20178 Click-to-Run)

    If you included in the Excel code the command to show the Templates and Add-ins dialog, that dialog appears as

    with none of the available add-ins listed.  Using DoEvents or introducing a time delay does not make any difference.

    Further, if you include the command to show the dialog twice, so that when you click on OK, it is dismissed and the re-opens, it still does not contain the list of available add-ins.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-05-18T03:26:23+00:00

    On Eileen's Lounge, Hans Vogelar suggested that a reference to the Word Object library is needed.

    I have a reference to the Office Object Model in Excel vba.

    Try, though, adding a reference to the Microsoft Word 16.0 Object Model in yours.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-05-18T03:26:13+00:00

    I can confirm that ribbon customizations don't show up when Word is started using Automation, although the add-in appears to be loaded.

    I'm using Word 2019 32-bit (in Office 2019 Professional Plus) on Windows 10 Home 64-bit. Both are fully updated.

    1. Word started manually.
    2. Word started using Automation from Excel.

    You can report this problem to Microsoft using File > Feedback > Send a Frown.

    This is not what I am seeing using Office 365 with the same build. They will load and operate. I will be able to try with an Office 2016 installation on Sunday.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-05-18T03:05:06+00:00

    Adding to the discussion...

    I am running a 32-bit version of Office and having no problems with the Merge Tools Add-In or the temporary one that I gave a link to.

    https://www.dropbox.com/s/0r1ltecxo8688c6/testB...

    So, it is not the 32-bit/64-bit distinction.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-05-18T01:52:16+00:00

    Hi Doug,

    Thanks again.

    Unfortunately this is not a matter of me changing versions. This add-in is used by one of my customers with >1000 systems. They're not going to change their Office version any time soon.

    It's not only the custom ribbon that is not working, but the add-in also contains some autoexec code which is not executed as well when Word is started from automation.

    I am planning to test tomorrow to see if changing to an application event might solve that.

    I also see the difference in the Account screen. Not showing a version when automation is used.

    I can see the same behaviour in Word 2016 64bits, not loading customizations and not executing an autoexec procedure.

    Was this answer helpful?

    0 comments