Appendix C: Child Properties

This refers to the CHILD PROPERTIES field which is available in the Transaction maintenance screens MNU_0030x.

This facility is only used in those transactions that can launch child processes via navigation buttons. It is designed to govern how the hitlist is handled in the parent process before it launches a child process that may wish to construct its own hitlist for the same database table.

Each entry should consist of a "name=value" pair, where "name" is the identity of a particular parameter, and "value" is the setting for that parameter.

Multiple entries can be specified by using "^" as a separator (eg: "A=1^B=2").

Possible options for handling the hitlist are:-

<blank>

Default UNIFACE behaviour. If the hitlist in the parent process is incomplete (ie: there are entries that match the current retrieve profile that have yet to be retrieved from the database) then all unfetched occurrences will be retrieved.

FOR LARGE DATABASE TABLES THIS COULD RESULT IN A SIGNIFICANT DELAY.

TRANSACTION=TRUE

Open up another database path for the child process, thus avoiding any conflicts with the hitlist.

THIS WILL RESULT IN MULTIPLE DATABASE OPENS FOR A SINGLE USER.

RELEASE=entity

Drop the hitlist for the named entity (the actual entity name should be identified in the transaction specification). If the current hitlist is incomplete then all unfetched occurrences will be dropped and will no longer be available in the current operation - the user will have to perform a <clear> followed by a <retrieve> in order to build a new hitlist.

At present these are the only choices available, and they are mutually exclusive.

http://www.tonymarston.net