I have a quite annoying problem with the autonew macro. I am using Word
2003.
In a template, i made the autonew macro, i tested it, and it does exactly
what it is supposed to do, as long as i am working directly in the .dot
file.
When i doubleclick the .dot file Word opens with a new document filled with
everything from the template, even the macro, but it's not firing up, and
when i go to Extra --> Macro --> Macro's... it is not showing the macro
anymore. If i then open Visual basic, all the code is there. Then if i add a
bit of extra code (another sub that just puts up a MsgBox with some crap)
suddenly all the macro's are usable again.
This kinda nullifies the use of the autonew macro as i still have to
manually add code and start it up. Does anyone have any clue why my macro
code is copied to the new document, but is not available for use until i
edit the code?
Regards,
M. Vlaardingerbroek
Jonathan West - 04 Aug 2006 15:13 GMT
>I have a quite annoying problem with the autonew macro. I am using Word
> 2003.
[quoted text clipped - 17 lines]
>
> M. Vlaardingerbroek
I suspect your security settings. Go to Tools, Macro, Security, and reduce
the level to medium.

Signature
Regards
Jonathan West - Word MVP
www.intelligentdocuments.co.uk
Please reply to the newsgroup
Keep your VBA code safe, sign the ClassicVB petition www.classicvb.org
M. Vlaardingerbroek - 07 Aug 2006 12:39 GMT
It wasn't security settings. I have no clue what it is though, but i copied
the total content of the .dot into a new file and it works perfectly. Some
of the templates are years old in this company and maybe some version
conflicts prevent it from working. I don't know, and i got it working in a
new file after ctrl+c ctrl+v so for me it's solved.
> >I have a quite annoying problem with the autonew macro. I am using Word
> > 2003.
[quoted text clipped - 20 lines]
> I suspect your security settings. Go to Tools, Macro, Security, and reduce
> the level to medium.