Oracle Forms Developer – Form Builder Reference, Volume 1

566
LOV1 and LOV2 are based on the same record group; LOV1 has Automatic Refresh set to Yes, LOV2
has Automatic Refresh set to No. When LOV1 is invoked, Form Builder executes the query to
populate the underlying record group. When the operator dismisses LOV1, Form Builder destroys the
record cache, and clears the record group.
When LOV2 is subsequently invoked, Form Builder again executes the query to populate the record
group, even though LOV2 has Automatic Refresh set to No. Because LOV2’s underlying record group
was cleared when LOV1 was dismissed, Form Builder does not consider it to have been queried by an
LOV invocation, and so re-executes the query.
If, on the other hand, both LOV1 and LOV2 had Automatic Refresh set to No, Form Builder would
execute the query when LOV1 was invoked, but would not re-execute the query for LOV2. This is
true even if the initial query returned no rows.
• When Automatic Refresh is set to No, you can programmatically replace the rows that were returned
by the initial query with POPULATE_GROUP. Form Builder ignores this operation when deciding
whether to re-execute the query. (Form Builder looks only at the internal flag that indicates whether
a query has occurred, not at the actual rows returned by that query.)
Automatic Refresh restrictions
Valid only for an LOV based on a query record group, rather than a static or non-query record group.