F
Frank Meulblok
Guest
"all context of any internal procedure which caused the error being lost" You mean the ABL stack trace ? In that case, you can use the -errorstack startup parameter / SESSION:ERROR-STACK-TRACE to get that stored in the exception objects, and retrieve it via the CallStack property of the Progress.Lang.Error object.
Continue reading...
Continue reading...