Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Word / Programming / June 2005

Tip: Looking for answers? Try searching our database.

Disable Toolbar and Menu Buttons

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
selliott - 07 Jun 2005 19:24 GMT
I am creating a procedure to customize our Word toolbars and menus (delete
Work menu, delete the Save icon from the Standard Toolbar and File menu), and
also reset a couple of key settings (e.g. Ctrl + S, Ctrl + P).  I am storing
this in a Word startup template.

I have a few questions about this procedure:

1.  I have it running on AutoExit, and am setting the CustomizationContext
to NormalTemplate.  I open the normal.dot file first within the code, and
then save it in the code after making the changes.  I am not sure if this is
a good idea or if it could eventually cause corruption if the normal.dot file
is opened and closed often enough.
2.  I could put it in an Autoexec module, but we have another AutoExec
module in a second startup template - will this cause any conflicts?

Thanks very much.
Jean-Guy Marcil - 08 Jun 2005 13:44 GMT
selliott was telling us:
selliott nous racontait que :

> I am creating a procedure to customize our Word toolbars and menus
> (delete Work menu, delete the Save icon from the Standard Toolbar and
[quoted text clipped - 4 lines]
>
> 1.  I have it running on AutoExit, and am setting the

Surely you mean AutoExec here...

> CustomizationContext to NormalTemplate.  I open the normal.dot file

Why open Normal.dot?

> first within the code, and then save it in the code after making the
> changes.  I am not sure if this is a good idea or if it could
> eventually cause corruption if the normal.dot file is opened and
> closed often enough.

It is possible.
Saving those changes in Normal.dot will only affect documents based on
Normal.dot. If the user creates a document based on another template, your
changes will not appear in those documents. Is that what you want?

> 2.  I could put it in an Autoexec module, but we have another AutoExec
> module in a second startup template - will this cause any conflicts?

Both will run.
Why not save the changes in the startup template? The changes on a toolbar
in a startup template are effective as long as the template is in the
startup folder. The only thing is you have to make sure that you do not have
contradicting AutoExec code that would cancel each other out...
Then, the changes you make will be valid as long as the Word session is on,
regardless of the templates used to create documents.

Signature

Salut!
_______________________________________
Jean-Guy Marcil - Word MVP
jmarcilREMOVE@CAPSsympatico.caTHISTOO
Word MVP site: http://www.word.mvps.org

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.