M
Mike Fechner
Guest
You throw an AppError – so you need to catch the AppError. Your catch is only for SysError. The rest looks o.k.! Von: OctavioOlguin [mailto:bounce-OctavioOlguin@community.progress.com] Gesendet: Montag, 9. Februar 2015 21:25 An: TU.OE.Development@community.progress.com Betreff: RE: [Technical Users - OE Development] On error .. throw: Catch... missing precious info. RE: On error .. throw: Catch... missing precious info. Reply by OctavioOlguin I did this, but it won't get to the message from the catch block, and neither to the last message of the original block , that means that it escaped form the block (I'm testing tin the scratch pad.) The avm noted the STOP as the "Stop was here" message is present, but it honors the condition and gets it done (to break the stack of programs?) Oddly enough, I don't get the messages realized, but I get the "Stop was here" message ... (where did it came from?) If we change SysError to AppErrror, the messge goes to parent frame and not to a alert-box... BLOCK-LEVEL ON ERROR UNDO, THROW. DO ON ERROR UNDO, THROW: RUN runfile. MESSAGE "Still runing original block" VIEW-AS ALERT-BOX. END. CATCH myS AS Progress.Lang.SysError: MESSAGE "Error file not found!!!: " myS:GetMessage(1). END CATCH. PROCEDURE RUNfile. DO ON STOP UNDO, RETURN ERROR NEW Progress.Lang.AppError ("Stop was here!", 0) . RUN asdfsd . END. END PROCEDURE. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...