Re: Checking datatype of CHAR variable in 4GL

> From marcog@linux.ctonline.it Sun Feb 15 06:05:50 1998 > From: Marco Greco <marcog@linux.ctonline.it> > To: yosemite@netcom.com > CC: informix-list@iiug.org > Subject: Re: Checking datatype of CHAR variable in 4GL > > That's exactly what I meant, Alan. Form errors (i.e. conversion errors, for > instance) are logged in the error log even after a WHENEVER ANY ERROR CONTINUE, > which obviously isn't the correct way of handling errors. Well, "correct" is a subjective term here. The "error log" is better considered a MESSAGE log, and the messages may or may not indicate actual errors that need attention. The log indicates when negative STATUS values have been encountered which, depending on program design and need, may or may not indicate an erroneous condition. IMHO, having more info is better than less, since you can choose to ignore those negative STATUS values that need no action on your part. From your perspective, perhaps this just gives you more "noise" that causes unnecessary interrupts. I don't know of a solution that satisfies us both here. > To make it more clear, this is the contents of my error log after running the > following useless program (4gl/c 4.16UC2 x SCO 3.2.5.0) > -- Alan Denney yosemite@netcom.com "I do not like this word 'bomb'. It is not a bomb. It is a device which is exploding." -- Jacques Le Blanc, French ambassador to New Zealand, referring to the nuclear 'devices' France is testing in the South Pacific