Your link states:
Quote:
|
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,
Quote:
|
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
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"?