Kbase P114113: FOR FIRST block is executed twice according to profiler output
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  3/9/2006 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
SYMPTOM(s):
FOR FIRST block is executed twice according to profiler output
FOR FIRST is actually only executed once
A unique FIND is done before the FOR FIRST statement
CAUSE:
The FIND causes a cursor to be created and the FOR FIRST causes the cursor to be repositioned. The profiler is seeing this as a second iteration of the FOR FIRST block when in fact it is a side effect of how the 4GL works.
FIX:
Define an alternate buffer for either the FIND or FOR FIRST statement so the the FOR FIRST does not have to cause a reposition of the cursor for the FIND statement.