Unhandled Exception Forms 6i

Question

Hi everyone,
I have created a form using Forms 6i and I added a button at the end of the form to bring values into 4 columns from another table to make a formula and then make a calculation between all these columns. Right now only one of these columns have values inside and the others are empty, but when I click on the button I receive the following error: FRM-40735: WHEN-BUTTON-PRESSED trigger raised unhandled exception ORA-01403
Is there a way to avoid this?
This is the code that I have in my button:
Begin
     FIRST_RECORD;
     LOOP
     SELECT CREDIT_VALUE, CREDIT_VALUE_Q2, CREDIT_VALUE_Q3, CREDIT_VALUE_Q4 INTO
     :CREDITO_UNO, :CREDITO_DOS, :CREDITO_TRES, :CREDITO_CUATRO
     FROM MY_TABLE
     WHERE SCHOOL_ID   =:SCHOOL_ID  AND
           CLASS_ID    =:CLASS_ID   AND
           TEACHER_ID  =:TEACHER_ID AND
           SCHOOL_YEAR =:PERIOD;
          EXIT WHEN :SYSTEM.LAST_RECORD = 'TRUE';
          NEXT_RECORD;
     END LOOP;
End;

Answer 1

InoL wrote:
Steve,
From what I understand from the OP, the block is already populated, and only a few items are calculated after the rows are retrieved. In that case, it would work.
Of course, it is probably much easier to use a post-query trigger and be done with all this looping stuff B-)
InoOh my word! You're right. I missed that point.
626836 should use his original method in the first post, or as you wrote, in a post-query trigger.
No matter where he selects those values, if he would enclose the select in a Begin-Exception-End, it would prevent the no_data_found errors.
626836, using your method:
BEGIN
  FIRST_RECORD;
  LOOP
    For C in
     ( Select CREDIT_VALUE, CREDIT_VALUE_Q2,
                 CREDIT_VALUE_Q3, CREDIT_VALUE_Q4
       FROM MATERIAS_ISS A, NOTAS_ISS B
       WHERE A.SCHOOL_ID   =:SCHOOL_ID
       AND   A.CLASS_ID    =:CLASS_ID
       AND   A.TEACHER_ID  =:TEACHER_ID
       AND   A.SCHOOL_YEAR =:SCHOOL_YEAR
       AND   A.SCHOOL_ID = B.SCHOOL_ID
       AND   A.CLASS_ID = B.CLASS_ID
       AND   A.TEACHER_ID = B.TEACHER_ID)
    Loop
      :CREDITO_UNO    := C.CREDIT_VALUE;
      :CREDITO_DOS    := C.CREDIT_VALUE_Q2;
      :CREDITO_TRES   := C.CREDIT_VALUE_Q3;
      :CREDITO_CUATRO := C.CREDIT_VALUE_Q4;
      -- always exit after populating the fields in the one row.
      Exit;
    End Loop;
    EXIT WHEN :SYSTEM.LAST_RECORD = 'TRUE'
    NEXT_RECORD;
  END LOOP;
END;Or this is less confusing. That inner loop above would be confusing to most people. You are only using the Loop structure to avoid select INTO. Besides, the code below takes fewer lines:
BEGIN
  FIRST_RECORD;
  LOOP
    BEGIN
      Select CREDIT_VALUE, CREDIT_VALUE_Q2, CREDIT_VALUE_Q3, CREDIT_VALUE_Q4
        into :CREDITO_UNO, :CREDITO_DOS,    :CREDITO_TRES,   :CREDITO_CUATRO
        FROM MATERIAS_ISS A, NOTAS_ISS B
        WHERE A.SCHOOL_ID   = :SCHOOL_ID
          AND A.CLASS_ID    = :CLASS_ID
          AND A.TEACHER_ID  = :TEACHER_ID
          AND A.SCHOOL_YEAR = :SCHOOL_YEAR
          AND A.SCHOOL_ID   = B.SCHOOL_ID
          AND A.CLASS_ID    = B.CLASS_ID
          AND A.TEACHER_ID  = B.TEACHER_ID;
      Exception When No_data_found then null;
    END;
    EXIT WHEN :SYSTEM.LAST_RECORD = 'TRUE'
    NEXT_RECORD;
  END LOOP;
END;Note that the Begin-Exception-End block of code could just have easily been placed in a post-query trigger, and it would work there just fine, only without the outer looping structure.