Difference: 0LASubrUtilFieldSet (3 vs. 4)

Revision 42012-02-29 - JeanNeron

Line: 1 to 1

META TOPICPARENT	name="APPXRuntimeSubroutineAPI"

.UTIL FIELD SET

Line: 29 to 29

<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.

Added:

>
>

Note: During debugging you will not be able to inspect the contents (via F11) of a field referenced using this API unless your process also has a reference in ILF to either the specific field (ie, a DISPLAY statement) or to the file containing the field (ie, READ/WRITE, etc) or to some other field in the same file (if the field is part of a file and not a work field).

Comments:

View topic | History: r6 < r5 < r4 < r3 | More topic actions...