Re: WHENEVER ANY ERROR

In article <5sgc4d$i1j@cssun.mathcs.emory.edu>, Jonathan Leffler <johnl@informix.com> writes >When you use STOP, the error message often (but not always) contains both >the file and the line number where the error occurred. Some errors are That's what really annoys me, sometimes I see Character to numeric conversion error appear whilst a program is running. BUT IT DOESN'T TELL ME WHERE!! >Basically, I agree with a lot of what you said... Same here, I prefer the stop on error and continue/check status after each sql statement/recover gracefully (E.g. back to previous screen in the app). More work but I think better than the whole program stopping. In my current job we use WHENEVER ERROR CALL function() syntax. Not bad and does trap all trapable errors. We use c4gl -anyerr on version 6.x so that our code all runs under version 4. > >Yours, >Jonathan Leffler (johnl@informix.com) #include <witticism.h> -- David Williams