Component Behavior
Specifies whether the component definition is cached in memory.
| Value | Meaning | Description |
|---|---|---|
K
|
Keep component definition in memory | Component definition remains in memory, making it faster to create a new component instance (using newinstance) |
Q
|
Drop component instance from memory | Component instance is dropped from memory. This is useful for small components (the difference in loading time from disk, as opposed to memory, is negligible) or for a component instance that will be used infrequently. |
S
|
Keep component instance and state in memory | Component instance and data is kept in
memory so it is still present when the component runs again. Note: Applicable only in Form components executed by the run command. Using run is not recommended. In older Uniface applications that use run instead of activate to execute components, this can be useful if the application continually uses the same data and you want to minimize I/O processing time by retrieving and formatting the data each time the component runs. Note: If the name of the component instance has been generated by Uniface (rather than being explicitly specified), the component definition cannot be reused and are always unloaded when the instance is deleted. |
