Ah, interesting. Yes this sounds like it could be the solution I require. It sounds like this is what macropod alluded to in his response. Of course, if the user has macros disabled due to security settings this wouldn't work, but that's the same problem as with any macro enabled document anyway.

Thanks very much I'll give that a try.



Thanks also to Charles Kenyon for his response - you mention some concerns that I share (user will overwrite the .docm).

It's similar. And, as I said, using it requires giving trusted access to the VBA project, which is a significant security risk.

Minimising that risk would require you to manually allow access, run the macro, then manually disallow access every time you want to create such a document; you can't automate the allow/disallow process; it has to be done manually.

Given those requirements, you may as well just copy the code across manually - which would require less work and no security exposure when you forget to disallow access after using the other approach. Or you could adopt the macro-enabled document approach Charles suggested.

Whichever approach you take, if the recipient is on a different system, they will have to allow macros to run. If they're on the same system, you could store the template in a trusted location the documents created from it can always access. That way, you won't have to add the code to every document, send the template or, generally, need users to enable macros.

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