Cannot save Building Block templates with project

[grNadpa]

Application.Templates( _
        "C:\Users\" & Environ("username") & "\AppData\Roaming\Microsoft\Document Building Blocks\1033\16\Building Blocks.dotx" _
        ).BuildingBlockEntries("aNotaryForm").Insert Where:=Selection.range, _
        RichText:=True

blows up with the error

Run-time error '5941': The requested member of the collection does not exist.

I figured out the reason is that neither

TemplateProject(Building Blocks) nor
TemplateProject(Built-in Building Blocks)

exist in my project window.
When I load them by inserting them from quick parts in the underlying document. They work fine. But when I save the application, and re-open, the template projects are missing.


Is there a way to keep them with the project? Or load the templates on instantiation?

[Charles Kenyon]

See Where can Building Blocks be stored?.
They must be in templates, not documents.
Here is information on how to insert them using code:
Using VBA to Insent an AutoText Entry or other Building Block

[grNadpa]

Your link states:

If you are in an ordinary document (not a template) and want to save a building block to it, first save it as a template (.dotx unless you also want macros) and then save the building block.

So, that is clearly part of the problem. And I suspect (as an old mainframe programmer) I'm getting tripped up on terminology -- specifically "macro".

I think, in the link you supplied,

Situation 1 - template holds both the building block and the macro

meets my needs if "macro" in this context is a generic term for "sub" and "function" that I can include within my form's code.

Without going into great detail here is what I have in development.
I have a userform that loads, instantiates, and unloads via command buttons the user's choice among a spreadsheet and two forms. One of the subordinate forms does the same for its two child forms. Three of those forms use building blocks stored in Quick Parts Gallery's Building Blocks.dotx in (custom) category "Waivers" named "aNotaryForm", "aPartialWaiver" and "aFinalWaiver".

Am I correct to expect that if I include the equivalent of your

Sub InsertMyBB()

into the form that uses "aNotaryForm" and the same code in the form that uses "aPartialWaiver" and so on that it should work if I save the whole "document" as "WaiverWorksheet.dotm"?

[Charles Kenyon]

Originally Posted by grNadpa

Your link states:

So, that is clearly part of the problem. And I suspect (as an old mainframe programmer) I'm getting tripped up on terminology -- specifically "macro".

I think, in the link you supplied, meets my needs if "macro" in this context is a generic term for "sub" and "function" that I can include within my form's code.

Without going into great detail here is what I have in development.
I have a userform that loads, instantiates, and unloads via command buttons the user's choice among a spreadsheet and two forms. One of the subordinate forms does the same for its two child forms. Three of those forms use building blocks stored in Quick Parts Gallery's Building Blocks.dotx in (custom) category "Waivers" named "aNotaryForm", "aPartialWaiver" and "aFinalWaiver".

Am I correct to expect that if I include the equivalent of your

Sub InsertMyBB()

into the form that uses "aNotaryForm" and the same code in the form that uses "aPartialWaiver" and so on that it should work if I save the whole "document" as "WaiverWorksheet.dotm"?

In Word, "macro" is pretty much synonymous with subroutine. It could be used to mean any vba code. It is not confined to recorded keystrokes.

As used in my page, I mean any code dealing with insertion of the building block. If the code is in the same template, then the location of the template containing the building block can always be identified as

ThisDocument.Fullname

in the code doing the insertion.

Yes. In Word jargon, a template is a particular kind of Word file. MS uses template to mean several things. See Templates in Microsoft Word.

[grNadpa]

Thank you, Charles Kenyon. (with, according to your imbedded comment, additional kudos to Timothy Rylatt)
Apparently all that was missing from my code was:

Application.Templates.LoadBuildingBlocks ' Thank you Timothy Rylatt

Thanks for the links. The "Situation 1" did not work, but Situation 3 did. And after stepping through the Situation 3 code, found that it ultimately resolved to the code I originally posted the exception of the statement you attribute to Rylatt.

Given that I insert the same building block item multiple times in my application, I'm not sure whether to use Rylatt's statement on each insertion or just the first one. But experimentation will solve that issue.

Again thank you so much for your patience and suggestions.