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

Re: Autonew macro doesn't fire on new document by Jonathan

Jonathan
Fri Aug 04 09:13:20 CDT 2006


"M. Vlaardingerbroek" <mv put the @ here vanderwaal-partners put the . here
nl> wrote in message news:44d34ab6$0$43799$58c7af7e@news.kabelfoon.nl...
>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


I suspect your security settings. Go to Tools, Macro, Security, and reduce
the level to medium.


--
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


Re: Autonew macro doesn't fire on new document by M

M
Mon Aug 07 06:39:19 CDT 2006

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.

"Jonathan West" <jwest@mvps.org> schreef in bericht
news:%23yi6uA9tGHA.4852@TK2MSFTNGP02.phx.gbl...
>
> "M. Vlaardingerbroek" <mv put the @ here vanderwaal-partners put the .
here
> nl> wrote in message news:44d34ab6$0$43799$58c7af7e@news.kabelfoon.nl...
> >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
>
>
> I suspect your security settings. Go to Tools, Macro, Security, and reduce
> the level to medium.
>
>
> --
> 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
>