Results 1 to 3 of 3
  1. #1
    New Lounger
    Join Date
    Feb 2001
    Location
    Gouda, Netherlands
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    macro not in normal.dot (word2000/win98)

    Amazing how good this lounge is - pity that the search function had to be interrupted, maybe this is an 'old' question. Phil mentioned that experts recommend saving macro's not in the normal.dot template, but in a separate. Why? And would that mean you have to work with your 'macro' template instead of normal.dot?

  2. #2
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts

    Re: macro not in normal.dot (word2000/win98)

    Some possible reasons for storing macros in a separate global template.

    <UL><LI>Normal.dot sometimes becomes corrupt and needs to be recreated
    <LI>You may want to share your macros with other people who won't want everything else in your Normal.dot
    <LI>If your macros are in a separate global template then you can disable them all very easily if you ever need to
    <LI>You may wish to add a digital signature to your macro template, but normal.dot can change quite frequently and this could be a nuisance[/list]If you install the macro template in word's startup folder then the macros are available all the time, you don't "attach" documents to global templates. You would only need to open your macro template if you want to edit your macros.

    StuartR

  3. #3
    Gold Lounger
    Join Date
    Dec 2000
    Location
    New Hampshire, USA
    Posts
    3,386
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: macro not in normal.dot (word2000/win98)

    The main reasons include:

    1. The larger the Normal template, the longer it takes Word to startup.
    2. You can make the Normal template read-only, which protects it from modification by erroneous/malevolent macros.
    3. Each application should have its own template if only to facilitate management and changes to the project. This includes macros, toolbars/menus and AutoText, not to mention styles that need to be used only fpor docs associated with the particular template.
    4. It is often necessary to add reference to other libraries/projects in a particular project. This is made more difficult i fth eNormal template is cluttered wit hsuch references, not to mention, reducing th echance of conflicts caused by have multiple references definging th esame object.
    5. On a multiuser system, if they so choose, users could be allowed to do whatever they wanna do wit the Normal template, and the code in the other templates can be protected from their prying eyes.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •