That update field trick is much needed. I could not see see what this was doing until I did this. I am a little confused as to how to apply this aside from copying and pasting it from a previous line though.
You’re not limited to copying-and-pasting; you could save the resulting field + text into a Quick Part to use in any document going forward. For instance, I have a document template that has embedded fields in the footer that count words and display the last saved date/time.
I've been trying without success to set the initial number to a number other than 1. For what I'm working on right now, for example, I need the numbering to begin at 94, not 1.
Use the switch \r to reset the first number in the sequence. In other words, instead of using the string with \n (as illustrated above), you’d put in “SEQ int * Arabic \r94” where “94” is the number you want to start with. And then you’d do the remaining SEQ codes exactly as shown in the illustration above, and they’ll number 95, 96, etc.
That update field trick is much needed. I could not see see what this was doing until I did this. I am a little confused as to how to apply this aside from copying and pasting it from a previous line though.
You’re not limited to copying-and-pasting; you could save the resulting field + text into a Quick Part to use in any document going forward. For instance, I have a document template that has embedded fields in the footer that count words and display the last saved date/time.
I've been trying without success to set the initial number to a number other than 1. For what I'm working on right now, for example, I need the numbering to begin at 94, not 1.
Use the switch \r to reset the first number in the sequence. In other words, instead of using the string with \n (as illustrated above), you’d put in “SEQ int * Arabic \r94” where “94” is the number you want to start with. And then you’d do the remaining SEQ codes exactly as shown in the illustration above, and they’ll number 95, 96, etc.
Make sense?