Difference: 0LASubrUtilFieldSet (2 vs. 3)
Revision 32012-02-29 - JeanNeron
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
.UTIL FIELD SET | ||||||||
| Line: 27 to 27 | ||||||||
| <value> is the string of data you want to set into the specified field (Required). | ||||||||
| Changed: | ||||||||
| < < | <value> must be appropriate for the type of field. For example, if the target field is an unsigned integer, then you cannot set real or negative numbers into it. If the value is too large, too small or has too many decimal places for the target field, it will not be set. If the target field is a token, you must pass a valid token value (case sensitive). Date/time fields must be a string in the format CCYYMMDDhhmmsstt. If any leading parts are not supplied, they must be replaced with a dash character, ie, '--120228' or '--------2241'. Trailing dashes are optional. | |||||||
| > > | <value> must be appropriate for the type of field. For example, if the target field is an unsigned integer, then you cannot set real or negative numbers into it. If the value is too large, too small or has too many decimal places for the target field, it will not be set. If the target field is a token, you must pass a valid token value (case sensitive). Date/time fields must be a string in the format CCYYMMDDhhmmsstt. If any leading parts are not supplied, they must be replaced with a dash character, ie, '--120228' or '--------2241'. Trailing dashes are optional. If the data cannot be moved into the target field, the previous contents of the target field will remain unchanged. | |||||||
See also .UTIL FIELD GET.
Comments: | ||||||||
View topic | History: r6 < r5 < r4 < r3 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback