[progress Communities] [progress Openedge Abl] Forum Post: Re: Trapping Error Messages...

  • Thread starter Thread starter Mike Fechner
  • Start date Start date
Status
Not open for further replies.
M

Mike Fechner

Guest
Hi Rob, I'll have to think more about the implications of your questions. But the most important thing is, that we can distinguish different STOP causes, especially STOP-AFTER and LOCK-WAIT-TIMEOUT. RUN a missing .p, CRC mismatch etc. are installation problems. And STOP-AFTER and LOCK-WAIT-TIMEOUT are caused by the application behavior, especially STOP-AFTER is more a feature than an issue. So I'd like to see a StopAfterError inheriting from Progress.Lang.Stop or Progress.Lang.StopError to be able to handle that specifically (very close to an OPEN-QUERY statement causing the STOP-AFTER).

Continue reading...
 
Status
Not open for further replies.
Back
Top