S
Susan L
I have created heading styles for appendices according to Shauna Kelley's
instructions. So, Word heading 7, 8, and 9 are the first, second, and third
level headings for appendices with numbering A, A.1, A.1.1, B -- etc.
When I insert a cross reference (numbered item) to an appedix in the body of
the document, it comes in preceded by a number, e.g., 6.5A, 6.5B or 1.2.5A,
1.2.5B, etc. This does not occur when a cross reference is inserted into an
appendix; there they appear correctly as A, B, C.
In a earlier version of the document, the cross references were working. Can
anyone shed some light on how I might correct this problem. (This document
will eventually serve as a template -- it only has two pages and the styles
that I have developed.)
Just as background, I was having some issues with Word (prompting to save
Normal.dot whenever I closed). This was resolved with the help of some MVPs
here by deleting the Data key in the registry. I don't know whether a
corrupted registry key could be behind this problem, but I did check my
template doc and it still have the cross reference issue.
instructions. So, Word heading 7, 8, and 9 are the first, second, and third
level headings for appendices with numbering A, A.1, A.1.1, B -- etc.
When I insert a cross reference (numbered item) to an appedix in the body of
the document, it comes in preceded by a number, e.g., 6.5A, 6.5B or 1.2.5A,
1.2.5B, etc. This does not occur when a cross reference is inserted into an
appendix; there they appear correctly as A, B, C.
In a earlier version of the document, the cross references were working. Can
anyone shed some light on how I might correct this problem. (This document
will eventually serve as a template -- it only has two pages and the styles
that I have developed.)
Just as background, I was having some issues with Word (prompting to save
Normal.dot whenever I closed). This was resolved with the help of some MVPs
here by deleting the Data key in the registry. I don't know whether a
corrupted registry key could be behind this problem, but I did check my
template doc and it still have the cross reference issue.