Correction: syntax processing does stop - only not in the first
procedure. Bad!
frans
On 11/15/19 8:47 PM, Frans Houweling wrote:
Hi,
I often see this message
"note: Warnings (n+1) exceed limit (n). Syntax processing will be
halted."
Luckily, syntax processing seems to go on anyway. I think the message
should just say "No more warnings will be issued" and syntax
processing should not be halted.
I am aware SET MXWARNS=0 suppresses all warnings - but I like to see
at least one (or possibly one per type).
Greetings
frans
