|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Hi,
I want to create a numeric field code, where I can specify the field name and control the format. What I want is to number tasks sequentially, as follows:
Task 1. Ttile task description blah blah
Task 2. Ttile task description blah blah
(and I am trying to use field codes to update the task numbers)
I have been using LISTNUM with my own field name "task", but it does not let me control the format (it always follows the field number with a parenthesis, which I don't want). It seems that the format is predefined for the "NumberDefault", "OutlineDefault", and "LegalDefault" names, but the documentation does not say how user-defined names are handled.
Is there a way I can control the format for my used-defined field name?
Also, the LISTNUM values seem to change when I do any re-formatting of lists elsewhere within the document.
More generally, which field code is best for a user-defined field (i.e., which one gives the user more control and breaks less often)? I have been trying SEQ and AUTONUMLGL, but they seem to have limitations.
Thanks,
Gabriel
|
|
Try using a SEQ field.
G.R. Toro wrote:
[Quoted Text] > Hi, > > I want to create a numeric field code, where I can specify the field name > and control the format. What I want is to number tasks sequentially, as > follows: > > Task 1. Ttile > task description blah blah > > Task 2. Ttile > task description blah blah > > (and I am trying to use field codes to update the task numbers) > > I have been using LISTNUM with my own field name "task", but it does not let > me control the format (it always follows the field number with a > parenthesis, which I don't want). It seems that the format is predefined > for the "NumberDefault", "OutlineDefault", and "LegalDefault" names, but the > documentation does not say how user-defined names are handled. > > Is there a way I can control the format for my used-defined field name? > > Also, the LISTNUM values seem to change when I do any re-formatting of lists > elsewhere within the document. > > More generally, which field code is best for a user-defined field (i.e., > which one gives the user more control and breaks less often)? I have been > trying SEQ and AUTONUMLGL, but they seem to have limitations. > > Thanks, > > Gabriel > >
|
|
Thanks.
Do you know of a good online example? I have questions about: a) How to initialize the counter b) How to control the format
Thanks,
Gabriel
"garfield-n-odie" <garfieldnodie[ at ]discussions.microsoft.com> wrote in message news:uc27QVpJGHA.1728[ at ]TK2MSFTNGP09.phx.gbl...
[Quoted Text] > Try using a SEQ field. > > G.R. Toro wrote: > >> Hi, >> >> I want to create a numeric field code, where I can specify the field name >> and control the format. What I want is to number tasks sequentially, as >> follows: >> >> Task 1. Ttile >> task description blah blah >> >> Task 2. Ttile >> task description blah blah >> >> (and I am trying to use field codes to update the task numbers) >> >> I have been using LISTNUM with my own field name "task", but it does not >> let me control the format (it always follows the field number with a >> parenthesis, which I don't want). It seems that the format is predefined >> for the "NumberDefault", "OutlineDefault", and "LegalDefault" names, but >> the documentation does not say how user-defined names are handled. >> >> Is there a way I can control the format for my used-defined field name? >> >> Also, the LISTNUM values seem to change when I do any re-formatting of >> lists elsewhere within the document. >> >> More generally, which field code is best for a user-defined field (i.e., >> which one gives the user more control and breaks less often)? I have >> been trying SEQ and AUTONUMLGL, but they seem to have limitations. >> >> Thanks, >> >> Gabriel >
|
|
Never mind. I was having trouble with SEQ fields, but all problems got resolved by pressing F9.
Thanks again,
Gabriel
"garfield-n-odie" <garfieldnodie[ at ]discussions.microsoft.com> wrote in message news:uc27QVpJGHA.1728[ at ]TK2MSFTNGP09.phx.gbl...
[Quoted Text] > Try using a SEQ field. > > G.R. Toro wrote: > >> Hi, >> >> I want to create a numeric field code, where I can specify the field name >> and control the format. What I want is to number tasks sequentially, as >> follows: >> >> Task 1. Ttile >> task description blah blah >> >> Task 2. Ttile >> task description blah blah >> >> (and I am trying to use field codes to update the task numbers) >> >> I have been using LISTNUM with my own field name "task", but it does not >> let me control the format (it always follows the field number with a >> parenthesis, which I don't want). It seems that the format is predefined >> for the "NumberDefault", "OutlineDefault", and "LegalDefault" names, but >> the documentation does not say how user-defined names are handled. >> >> Is there a way I can control the format for my used-defined field name? >> >> Also, the LISTNUM values seem to change when I do any re-formatting of >> lists elsewhere within the document. >> >> More generally, which field code is best for a user-defined field (i.e., >> which one gives the user more control and breaks less often)? I have >> been trying SEQ and AUTONUMLGL, but they seem to have limitations. >> >> Thanks, >> >> Gabriel >
|
|
You use the \r switch to reset the number to the number following the r
{ SEQ test \r2 }
will cause the sequence to start at 2
I am not sure what you mean by format, but, addition of the following switches will cause the following
{ SEQ test \* Arabic } gives 1, 2, 3 \* roman gives i, ii, iii \* ROMAN gives I, II, III \* alphabetic gives a, b, c \* ALPHABETIC gives A, B, C \* Ordinal gives 1st, 2nd, 3rd \* CardText gives One, Two, Three \* OrdText gives First, Second, Third
etc. Click on the Options button in the Insert Field dialog when the SEQ field is selected to see more.
then if you add a \* Charformat switch, the character formatting that you apply to the S of SEQ will be applied to the number -- Hope this helps.
Please reply to the newsgroup unless you wish to avail yourself of my services on a paid consulting basis.
Doug Robbins - Word MVP
"G.R. Toro" <toro[ at ]riskengXYZ.com> wrote in message news:zcmdnaCji9EbKELenZ2dnUVZ_vudnZ2d[ at ]megapath.net...
[Quoted Text] > Thanks. > > Do you know of a good online example? I have questions about: > a) How to initialize the counter > b) How to control the format > > Thanks, > > Gabriel > > > > "garfield-n-odie" <garfieldnodie[ at ]discussions.microsoft.com> wrote in > message news:uc27QVpJGHA.1728[ at ]TK2MSFTNGP09.phx.gbl... >> Try using a SEQ field. >> >> G.R. Toro wrote: >> >>> Hi, >>> >>> I want to create a numeric field code, where I can specify the field >>> name and control the format. What I want is to number tasks >>> sequentially, as follows: >>> >>> Task 1. Ttile >>> task description blah blah >>> >>> Task 2. Ttile >>> task description blah blah >>> >>> (and I am trying to use field codes to update the task numbers) >>> >>> I have been using LISTNUM with my own field name "task", but it does not >>> let me control the format (it always follows the field number with a >>> parenthesis, which I don't want). It seems that the format is >>> predefined for the "NumberDefault", "OutlineDefault", and "LegalDefault" >>> names, but the documentation does not say how user-defined names are >>> handled. >>> >>> Is there a way I can control the format for my used-defined field name? >>> >>> Also, the LISTNUM values seem to change when I do any re-formatting of >>> lists elsewhere within the document. >>> >>> More generally, which field code is best for a user-defined field (i.e., >>> which one gives the user more control and breaks less often)? I have >>> been trying SEQ and AUTONUMLGL, but they seem to have limitations. >>> >>> Thanks, >>> >>> Gabriel >> > >
|
|
|
|
|