L
Lieven De Foor
Guest
Apparently this is a known issue, see KB knowledgebase.progress.com/.../P84367 It's really baffling that Progress catalogs this as 'expected behaviour'. For me this is a bug, and not a small one. I should be able to reliably use ON ERROR/CATCH blocks to catch ALL errors, without the need to add NO-ERROR and check for NUM-ENTRIES everywhere (because Progress can't provide a list of statements that could exhibit this behavoir). If I can write code to check for NUM-MESSAGES and in response throw a new error that can be caught, then why can't Progress do this on a lower level?
Continue reading...
Continue reading...