G
George Potemkin
Guest
> Anyway it would have been great if the ABL just would have allowed the ENTRY(2 in the for each 
The question is: would we be happy if ABL will silently ignore the errors in the functions inside the WHERE clause or should it inform us when something goes wrong? The simplified example: FUNCTION MyFunc RETURNS CHARACTER. /* RETURN ENTRY(2,"A,a"). */ /* RETURN ERROR. */ RETURN ENTRY(2, "a"). /* DEFINE VARIABLE f AS CHARACTER NO-UNDO. ASSIGN f = ENTRY(2,"a") NO-ERROR. IF ERROR-STATUS:ERROR THEN RETURN ERROR. ELSE RETURN f. */ END FUNCTION. DEFINE TEMP-TABLE tt FIELD f1 AS CHARACTER. DO TRANSACTION: CREATE tt. ASSIGN f1 = "a". END. FOR EACH tt WHERE f1 EQ MyFunc(): DISPLAY tt. END
Continue reading...
The question is: would we be happy if ABL will silently ignore the errors in the functions inside the WHERE clause or should it inform us when something goes wrong? The simplified example: FUNCTION MyFunc RETURNS CHARACTER. /* RETURN ENTRY(2,"A,a"). */ /* RETURN ERROR. */ RETURN ENTRY(2, "a"). /* DEFINE VARIABLE f AS CHARACTER NO-UNDO. ASSIGN f = ENTRY(2,"a") NO-ERROR. IF ERROR-STATUS:ERROR THEN RETURN ERROR. ELSE RETURN f. */ END FUNCTION. DEFINE TEMP-TABLE tt FIELD f1 AS CHARACTER. DO TRANSACTION: CREATE tt. ASSIGN f1 = "a". END. FOR EACH tt WHERE f1 EQ MyFunc(): DISPLAY tt. ENDContinue reading...