Hi Ken:
Yes.
This is a "corrupt document" or "corrupt template" problem. The numbering
List Templates have gone bad.
1) Quit Word (it must be entirely quit)
2) Find the document template and rename it.
3) Find your Normal Template and rename it.
Now try the operation again on a blank document. If it's OK, the problem is
in the document you were trying to work on.
4) Open it
5) Save it as a Web Page
6) Close and re-open the Web Page version
7) Save it as a document.
That will fix it.
The problem is that the numbering in a Word document is similar to a style:
it's a complex and fragile structure that can sometimes corrupt. And when
it does, it can sometimes contain conflicting definitions that can crash
Word.
The numbering definitions are stored in a hierarchy. The most immediate
store is the section break following the numbered list. This is not often a
"lot" of help, because the numbered list that has corrupted is often no
longer in the document.
The next store is in the section break hidden below the last paragraph mark
in the document. Copying all but the last paragraph mark to a new document
will fix the problem, provided it has not migrated outwards.
The next closest store is the template attached to the document. Next to
that is the Normal template. And finally the Word Preferences .plist.
The corruption can exist in any of these places. Re-installing will not fix
the problem unless you first run the Remove Office utility from the Office
CD, because the re-installation routine is designed not to replace existing
files. That's why we re-name the templates.
Reverting to an earlier version of Word will not necessarily fix the problem
either, because the earlier version will use the same corrupt files the new
version does.
Hope this helps
In Word 11.1.0 under OS X 10.3.6, the program crashes every time I choose
Format:Bullets and Numbering, and then click the Outline Numbered Tab. The
program also crashes if I access Outline Numbered in any other way. "Smart
buttons" that call the numbering function also cause the program to crash
every time. Does anyone have a solution for this (other than returning to
10.1.6)?
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <
[email protected]>
Consultant Technical Writer
Sydney, Australia +61 4 1209 1410