L
Laura Stern
Guest
These statements have a very specific and well defined behavior. You learn what each statement does and code it the way you want it to behave. So your statement: "So when using structured error handling, my recommendation will be to avoid mixing with classic RETURN ERROR unless you know you want the RETURN ERROR behaviour." is kind of peculiar. Yes, of course - as I just said, you learn what the statements do first, then you code so that it does what you want! And BTW - this is always what RETURN ERROR has done. It returns first and then raises error. So if you were in an DO ON ERROR block, it would not follow the ON ERROR directive of that block, it would return and then raise error and abide by whatever error handling was in the caller. Not very mysterious. What do you mean by: "problems with multi block-level ON ERROR UNDO, THROW, where none of the CATCH executes"?
Continue reading...
Continue reading...