Forum Discussion

KenK1110's avatar
KenK1110
Copper Contributor
Jun 13, 2026

Word Templates Opening Multiple Times

Recently upgraded some templates from Word 2010 and 2003 (yeah, I know) to 2016 and 365 with, frankly, disappointing results. :o/

 

Since 2003 we've been using a pair of macros to merge some smaller files, doing some automated and manual clean up then running another macro that saves them back to the individual files. BUT, in 2016 and 365 when the macro creates a new document with the very basic command like this:

 

Set NewDoc = Documents.add TemplateName.dotm

 

A new document is created with the template attached, but as soon as it's saved, THE TEMPLATE IS NO LONGER ATTACHED! The only way to get the template to stay attached is to give the full path of the template, which then opens (inexplicably) a second version of the template. There are time when Word gives messages during macros that the template is read-only when a new document is created based on the template.

 

Isn't that kind of the whole purpose of a template? To create similar documents based on, gosh, well, a TEMPLATE?!

 

Is this all new "security" (and I use the term lightly) measures?

 

Does anyone know if there is a way to make the "modern" versions of Word work like to the "good 'ol days" where templates just worked and Word didn't open multiple versions of the same template file and give read-only messages?

 

With the help of a network admin we've done everything we could think of to try and convince Word that various network drives are "safe."

 

Sorry for the snark, but it is immensely frustrating that code we've relied on 20 years all of a sudden doesn't work.

 

Thanks for any ideas or insights.

 

Best,
-Ken

9 Replies

  • Estorehf's avatar
    Estorehf
    Brass Contributor

    To work around this, you might try explicitly attaching the template after document creation using the AttachTemplate method, or consider setting the template's path as a full UNC path with proper permissions.

  • Several times a day I click on a ribbon button that runs the command:

     

    Sub CreateInvoice(control As IRibbonControl)

    Documents.Add "000-Merge Tools Invoice.dotm"

    End Sub

     

    and have been doing so for more than 15 years over which time I have moved from probably Office 2010 up to now Microsoft 365, without experiencing the issue that you mention.

     

    While I usually have no reason to save the documents so created as Word documents (as I save them in PDF format) I have just now saved one as a Word document (.docx) that I have closed, re-opened. closed, restarted the computer and re-opened the document and in each case, after opening the document and going to the Developer Tab > Document Template, the template that is attached to the document is the one from which it was originally created, as shown by the following screen shot

    Likewise, in the Visual Basic Editor, the  Project for the document contains a reference to the template from which it was created

    Can you zip up a copy of the template with which you experience that issue and post it here, or send it to me at mergetools [atsymbol] gmail dot com and I will investigate the issue.

  • In modern Word, templates behave differently than in old say 2003,2010: documents created with Documents.Add no longer retain the template link unless the full path is specified, and network locations often trigger “read-only” or duplicate template loads due to new security and trust center policies, support.microsoft.com/en-us/word/create-a-template

    • Kidd_lp

      I am not sure what you mean by "modern Word", but in Word in Microsoft 365 Apps for enterprise when used on the desktop, there has been absolutely no change in the way that templates behave when using a command such as:

      Documents.Add "000-Merge Tools Invoice.dotm"

      For more information, see my response to the OP.

       

      • KenK1110's avatar
        KenK1110
        Copper Contributor

        Sorry, just getting back to this. Thanks for responding guys.

         

        Things are ABSOLUTELY different. Kidd_Ip may have hit the nail on the head regarding network locations. And he's absolutely right with the template not staying attached unless the full path is used, which then causes the read-only message, at least on a network drive. Which is REDICULOUS!

         

        I've not yet tried everything I'm having trouble with working only locally. Which, honestly, should NOT be a requirement and really isn't an option, I don't want to have to continually distribute templates. The Workgroup templates folder (or whatever it's called) in the options should be treated as safe a location as my local drive. IT'S MY INTERNAL NETWORK, DAMMIT, LET ME USE IT!!!

         

        Also, if anyone has insight into the speed at which some macros run I'd appreciate help there to. I have one macro that finishes in 11 seconds in 2010, but takes almost an minute and half in 365. I've not yet tried to Google things to see if there are options in 365 that need turning off when macros run. When I have time to do so I'll post back if I find anything.

         

        Thanks for listening to me wine and thanks again for responding.

         

        Ken