WD98: New Code Lost When Word Started with SHIFT Key (176996)
The information in this article applies to:
- Microsoft Word 98 Macintosh Edition
This article was previously published under Q176996 SYMPTOMS
When you start Word while holding down the SHIFT key (when you hold down
the SHIFT key, the Normal template is not loaded), and then create a macro
that you want to save as part of the Normal template, the macro will be
lost when you exit and restart Word.
CAUSE
When you start Word while holding down the SHIFT key, the following occurs
concerning macro functionality:
- Previously saved code is not visible.
- Newly entered code is not saved.
- No warning is given about the loss of newly entered code.
WORKAROUND
Before you attempt to create a new Visual Basic for Applications macro,
subroutine, or function, close and restart Word (do not hold down the SHIFT
key when you restart Word).
CAUTION: IF you have started Word holding the SHIFT key and you attempt to
save newly created macro code to the Normal template (while in the Visual
Basic Editor, on the File menu click Save Normal), you will be prompted to
overwrite your existing Normal template. If you choose to overwrite, all
macros and customizations in the existing Normal template will be lost.
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article. We are researching this problem
and will post new information here in the Microsoft Knowledge Base as it
becomes available.
MORE INFORMATION
Holding down the SHIFT key while starting Word disables everything
including the Normal template. Starting Word this way ignores the existing
Normal template and creates a "blank" Normal template which you are then
prompted to save when you quit Word. (This is equivalent to starting Word
for Windows with the /a switch.)
Holding down SHIFT+OPTION disables auto-run macros but still opens the
existing Normal template.
Holding down either SHIFT or SHIFT+OPTION will disable any Auto macros.
Modification Type: | Major | Last Reviewed: | 10/4/2002 |
---|
Keywords: | kbbug KB176996 |
---|
|