If it's a true template, it would have a dotm extension, not docm. That said, what you're describing is the normal behaviour for a document created from a template. If you want the macros to travel with the document, you'll have to add them to the document - and save it in the docm format. Although this could be done programmatically, it would require giving 'trusted access' to the VBA project environment, which is a significant security risk for you. Otherwise, you could send both the document and the template - which the recipient would need to copy to their own templates folder (not a simple task for most users) so the macros would once again be available to the document.

__________________
Cheers,
Paul Edstein
[Fmr MS MVP - Word]

Thanks for replying to my question. Yes you're right, it's a .dotm file, I made a mistake in my post.

Ah ok. That's a shame, as I lose the advantages of the template.

I'm not sure I've understood this part of your reply. The functionality I was hoping for is that the template, which contains the helper macros, would transfer these macros to the new document when it is opened. Whether those macros actually run or not would still be dependent upon the macro security settings of the user installation, of course.


Ok thanks. I understand from your reply that the functionality I was hoping for does not exist, and in order to replicate the behaviour I have on my installation I'd have to give instructions for users to copy the .dotm to their templates folder.
Otherwise, I'd have to distribute a .docm, and then the macros would be available, but in that instance it is likely that someone will eventually overwrite the document (which is why a template is useful in the first place).

I guess another option is to use a .docm file and version control it. But getting the users to understand version control... hmmm.

Many thanks again for your response.