Charles
Tue Aug 10 07:54:58 CDT 2004
You might use a separate installer template that as part of its AutoExec
strips the macros, toolbars, and keyboard shortcuts from Normal.dot and
saves normal.dot. Then put in your Add-In. Again, in my experience, keyboard
shortcuts and toolbars are set to call a particular project and module so
your problem is not merely which macro Word defaults to but which your
shortcuts and toolbars reach. They do not necessarily follow the default
path for Word.
--
Charles Kenyon
Word New User FAQ & Web Directory:
http://addbalance.com/word
Intermediate User's Guide to Microsoft Word (supplemented version of
Microsoft's Legal Users' Guide)
http://addbalance.com/usersguide
See also the MVP FAQ:
http://www.mvps.org/word which is awesome!
--------- --------- --------- --------- --------- ---------
This message is posted to a newsgroup. Please post replies
and questions to the newsgroup so that others can learn
from my ignorance and your wisdom.
"Francois Piette" <francois.piette@overbyte.be> wrote in message
news:41189cda$0$311$4d4efb8e@read.news.be.uu.net...
> > How are you running the macros? If you are using "application.run
> > macroname:=" statements or triggering them with a toolbar button there
> > should be little problem. If the former, refer to the project and module
> > along with the name of the macro in the statement. I do not know the
> syntax
> > for this, but know it exists.
>
> Some macros are triggered by a toolbar button and some other by kyboard
> shortcut.
>
> > If you don't have unique names for your
> > project and module, you have a problem.
>
> I currently have macros in normal.dot that I would like to move to a
startup
> template for easy distribution. So I'm looking for a way to either:
> - Be sure that the macros from startup template has higher priority
> - Automatically delete the macros from normal.dot so that those in the
> template are used.
>
> As mentionned before, my problem is that I have 500 workstations using the
> application and have to find a way to automate this "update". I can
> automatically distribute the startup template or any separate executable
> application at the user workstation. I can easily spent several days
> developping something to automate the update process and then avoid going
to
> 500 workstations (you imagine the time needed for 500 workstations !).
>
> --
> francois.piette@overbyte.be
> Author of ICS (Internet Component Suite, freeware)
> Author of MidWare (Multi-tier framework, freeware)
>
http://www.overbyte.be
>
>
>
> "Charles Kenyon" <msnewsgroup@remove.no.spam.addbalance.com> a écrit dans
le
> message de news:eAYsBPlfEHA.3916@TK2MSFTNGP11.phx.gbl...
> > Your questions are not stupid. As I said in my signature, I am somewhat
> > ignorant myself in this area.
> >
> > How are you running the macros? If you are using "application.run
> > macroname:=" statements or triggering them with a toolbar button there
> > should be little problem. If the former, refer to the project and module
> > along with the name of the macro in the statement. I do not know the
> syntax
> > for this, but know it exists. If you don't have unique names for your
> > project and module, you have a problem.
> >
> > If you are triggering them from a menu or toolbar button, actually
create
> > the button (manually) in the Add-In and it will not get confused. It
will
> > pull the macro that it was created with even if there are confusing
names.
> > "Francois Piette" <francois.piette@overbyte.be> wrote in message
> > news:41172af7$0$306$4d4efb8e@read.news.be.uu.net...
> > > > 1) You should _not_ have your Add-In mess around with normal.dot.
> > > > Name your macros so that the name will be unique. It isn't hard.
> > >
> > > That answer will not help at all. There is an existing situation and I
> > must
> > > work with that situation. I have 500 workstations with that situation
> and
> > I
> > > don't want to manually change anything (imagine the time needed to sit
> > down
> > > in front of 500 workstations and clean the mess up !).
> > >
> > >
> > > > 2) Generally it has been my experience that a macro in the document
> will
> > > be
> > > > run in preference to a macro of the same name in the attached
> template.
> > A
> > > > macro in the attached template will be run in preference to one in
any
> > > > global template. A macro in normal.dot will be run in preference to
> one
> > in
> > > a
> > > > global template other than normal.dot. If you have multiple globals,
> it
> > > > seems to depend on the order in which they are loaded.
> > >
> > > OK. So it is unreliable.
> > >
> > > And what about my other questions:
> > > > > How can I manage to have the macros in the template located
> > > > > in the startup folder detect that macro name conflict exist ?
> > > > > And better, how can a macro in the template remove a
> > > > > macro in normal.dot ?
> > >
> > > I could add that I can easily write an external program making use on
> COM
> > to
> > > driver Word to remove/rename/create those macro, if it is easier. I
have
> a
> > > working system to remotely distribute and run the external program
> > > automatically on the 500 workstations.
> > >
> > > Thank you for taking time to answer my [stupid] questions.
> > >
> > > --
> > > francois.piette@overbyte.be
> > > Author of ICS (Internet Component Suite, freeware)
> > > Author of MidWare (Multi-tier framework, freeware)
> > >
http://www.overbyte.be
> > >
> > >
> >
> >
>
>