Discussion:
Paragraph [0100] rollover problem
(too old to reply)
Joel
2006-08-14 16:07:25 UTC
Permalink
Hello, I'm new to the newsgroup, but have read quite a few of the
webpages that you link to in the FAQ. Here is a description of the
problem:

I have paragraph numbering in my document which I have defined in the
"Bullets and Numbering" format section. I have customized the field to
look like:

[0001] text
[0002] text
...
[0010] text

The problem occurs at pargraph 100, which under the scheme outline
above will look like this without modification:

[00100] text

so, it does not keep the four number system that I have implemented and
as a result of the extra number, a new tab is introduced. I can fix
this by making a new numbering scheme at 100, but obviously this
introduces problems during revisions where a new paragraph is added
before paragraph 100. Are there any known solutions to this problem?

Thanks!
Joel Stevens
John McGhie [MVP - Word and Word Macintosh]
2006-08-15 10:52:23 UTC
Permalink
Hi Joel:

There are several solutions to this problem, but you cannot easily do that
with a List Template (which is what Format>Bullets and Numbering is using)
because you cannot add the "edit codes" required to get the leading zeros to
print.

You can do this with SEQ fields or with ListNum fields.

Look for a help topic named "Numeric Picture (\#) field switch" and see if
that will do what you want.

Cheers


On 15/8/06 2:07 AM, in article
Post by Joel
Hello, I'm new to the newsgroup, but have read quite a few of the
webpages that you link to in the FAQ. Here is a description of the
I have paragraph numbering in my document which I have defined in the
"Bullets and Numbering" format section. I have customized the field to
[0001] text
[0002] text
...
[0010] text
The problem occurs at pargraph 100, which under the scheme outline
[00100] text
so, it does not keep the four number system that I have implemented and
as a result of the extra number, a new tab is introduced. I can fix
this by making a new numbering scheme at 100, but obviously this
introduces problems during revisions where a new paragraph is added
before paragraph 100. Are there any known solutions to this problem?
Thanks!
Joel Stevens
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <***@mcghie.name>
Microsoft MVP, Word and Word for Macintosh. Consultant Technical Writer
Sydney, Australia +61 (0) 4 1209 1410
Stefan Blom
2006-08-17 11:14:07 UTC
Permalink
The following SEQ field code can be used to produce numbers [0001],
[0002], ..., [0010], [0011], ..., etc:

{ SEQ test \# "[0000]" }

To insert the field delimiters, {}, press Ctrl+F9. Type the code as
shown. (Note, however, that "test" is the SEQ field identifier, and
you can choose a more meaningful name for your list. A document can
have several different sequences; just use different identifiers for
them.) Press F9 to update. You can use copy and paste to insert more
fields.

SEQ fields don't update automatically, which will be especially
apparent if you use copy and paste to duplicate them. To force an
update of SEQ as well as other fields, select the whole document and
then press F9. Also, fields are updated as you switch to Print
Preview.
--
Stefan Blom
Microsoft Word MVP
Post by Joel
Hello, I'm new to the newsgroup, but have read quite a few of the
webpages that you link to in the FAQ. Here is a description of the
I have paragraph numbering in my document which I have defined in the
"Bullets and Numbering" format section. I have customized the field to
[0001] text
[0002] text
...
[0010] text
The problem occurs at pargraph 100, which under the scheme outline
[00100] text
so, it does not keep the four number system that I have implemented and
as a result of the extra number, a new tab is introduced. I can fix
this by making a new numbering scheme at 100, but obviously this
introduces problems during revisions where a new paragraph is added
before paragraph 100. Are there any known solutions to this
problem?
Post by Joel
Thanks!
Joel Stevens
m***@yahoo.com
2006-09-12 19:52:13 UTC
Permalink
Is there some way to put the { SEQ } into a "Style" so that when the
style is in use, a new paragraph is prepended by an incremented,
leading zeroed, number? Inserting the { SEQ } in hundreds of
paragraphs is a mind-numbing use of a computer, whether you use
autotext or not.

If possible, please email me with responses when posting.
Post by Stefan Blom
The following SEQ field code can be used to produce numbers [0001],
{ SEQ test \# "[0000]" }
Post by Joel
[0001] text
[0002] text
...
[0010] text
The problem occurs at pargraph 100, which under the scheme outline
[00100] text
so, it does not keep the four number system that I have implemented
and
Post by Joel
as a result of the extra number, a new tab is introduced. I can fix
this by making a new numbering scheme at 100, but obviously this
introduces problems during revisions where a new paragraph is added
before paragraph 100. Are there any known solutions to this
problem?
Post by Joel
Thanks!
Joel Stevens
John McGhie [MVP - Word and Word Macintosh]
2006-09-14 12:52:07 UTC
Permalink
No. Sorry :-)


On 13/9/06 5:52 AM, in article
Post by m***@yahoo.com
Is there some way to put the { SEQ } into a "Style" so that when the
style is in use, a new paragraph is prepended by an incremented,
leading zeroed, number? Inserting the { SEQ } in hundreds of
paragraphs is a mind-numbing use of a computer, whether you use
autotext or not.
If possible, please email me with responses when posting.
Post by Stefan Blom
The following SEQ field code can be used to produce numbers [0001],
{ SEQ test \# "[0000]" }
Post by Joel
[0001] text
[0002] text
...
[0010] text
The problem occurs at pargraph 100, which under the scheme outline
[00100] text
so, it does not keep the four number system that I have implemented
and
Post by Joel
as a result of the extra number, a new tab is introduced. I can fix
this by making a new numbering scheme at 100, but obviously this
introduces problems during revisions where a new paragraph is added
before paragraph 100. Are there any known solutions to this
problem?
Post by Joel
Thanks!
Joel Stevens
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.

John McGhie <***@mcghie.name>
Microsoft MVP, Word and Word for Macintosh. Business Analyst, Consultant
Technical Writer.
Sydney, Australia +61 (0) 4 1209 1410
Loading...