D
dbeavon
Guest
Cool. I'll try that out. I would prefer to have a future-proof'ed version of an "untrappable STOP". But I guess it is unlikely that anyone will include new STOP handling at the start of the callstack (batch, chui, appserver, whatever) unless they *really* know what they are doing. As far as I'm aware, the only ABL conditions we check for and handle on a regular basis are ON ERROR and ON ENDKEY. (In ABL you have to put these on *every* single FOR EACH loop or you get the agonizing behavior where only *one* iteration of the loop is undone and the program keeps going on its merry way. But that is a separate topic altogether.) Thanks for the help, David
Continue reading...
Continue reading...