When you create a new document in Word, it automatically bases on a template. By default, this will be the built-in Normal.dotm, but it can be any *.dotx or *.dotm file. This document will maintain a link back to the template, enabling it to use Building Blocks, Ribbon customization and macros in the template.

Users and companies provide templates for specific, oft-occurring tasks. In order to make them easily discoverable, they should appear in the interface presented for creating a new document. With the exception of Word 2007, that had an “Office button” rather than a File menu, this interface is accessed via the command File/New.

Up until the introduction of the Backstage in Office 2010, this interface was the File New dialog box. In Office 2010 and 2013, it’s a Backstage view, but in Word 2010 you have to click the link “My templates” in order to access custom templates, which are still offered in the File New dialog box. In Word 2013, custom templates are listed in the Backstage view in the “Personal” list (below), but not necessarily all of them. Why this is, is the topic of this post.

Templates2013_New

Where custom templates should appear in the templates listing and what priority they should have has always been a topic of much discussion, but generally it is important that custom templates are accessible through this interface. In this respect, Word 2013 represents a definite improvement over Word 2010 in that you don’t have to change the interface (go from the Backstage to a dialog box).

You aren’t restricted to the Backstage view, it’s also still possible to display the old File/New dialog box in Word 2010 & 2013, using the object model: Application.Dialogs(wdDialogFileNew).Show. Disturbingly, this interface also not does display all the templates – the listing that appears here is different from the one in the Backstage.

What’s the reason for this discrepancy?

There has always been an installation default for the location of the user’s templates, but this can be changed using the “File locations” dialog box, as pictured below. Since the introduction of Word 2007, the button to open the dialog box is located in File/Options/Advanced/General.

Templates_old1

It turns out that all the templates saved in this location appear in the old File/New dialog box, but not in the Backstage listing.

Word 2013 has introduced a new option for the default location to save templates, in File/Options/Save. (When you choose “template” as the file type in File/Save As, Word will automatically choose this location.) Templates saved to this folder appear in the Backstage view, but not in the File/New dialog box. So in order to have all the templates appear in both the dialog box and in Backstage, both file paths need to be the same.

Templates2013

It is interesting to note that Excel and PowerPoint share these default template locations. Also, Excel shares the setting in the File Locations dialog box for templates listed in its old File/New dialog box.

While it is possible to access the entry in the old File Locations dialog box using Word’s object model – Application.Options.DefaultFileLocation(wdUserTemplatesPath) – it appears no way has been to access this new location information.

It is, however, available over the Registry in HKEY_Current_User\Software\Microsoft\Office\15.0\Word\Options. So you can read/write the value using VBA like this:
System.PrivateProfileString("", _
"HKEY_Current_User\Software\Microsoft\Office\15.0\Word\Options", _
"PersonalTemplates")
2 Responses to “Word 2013: Templates location and File/New”
  1. Tim Jeffryes says:

    This is useful. I am looking for some VBA this is related but not exactly the same. It seems when launch word 2013 for the first time, the word “Personal” does not even appear under templates. I’d like to know if there is some VBA that can ensure that “personal” appears.

    • WordMeister says:

      Hi Tim
      I don’t know of any VBA that can change what appears in the Backstage. That stuff is pretty much “off-limits” to any developer interface. You might have better luck getting suggestions in the TechNet forums. There might be a Registry setting, for example.

  2.  
Leave a Reply