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. 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) main define a smallint whenever any error continue call startlog("error.log") let a="a" end main Date: 02/15/1998 Time: 14:56:48 FORMS statement error number -1213. Character to numeric conversion error Ciao, Marco _______________________________________________________________________________ Marco Greco, Catania, Italy marcog@linux.ctonline.it rem radioterapia +39 95 447828 fax 446558 Informix faq http://www.iiug.org/techinfo/faq/informix.htm 4glworks http://www.ctonline.it/~marcog Informix on Linux http://www.ctonline.it/~marcog/ifmxlinux.htm Alan Denney wrote: > > In article <6c1tbj$2h5$1@news.xmission.com>, > Marco Greco <marcog@linux.ctonline.it> wrote: > >Nice try Jack. > >That's what I've been doing for a long time, until I discovered that, starting > >from 4gl 4.13, non fatal errors where added to the error log all the same :-( > > Um, that's what the log is there for. > > The point is: the program flow itself is unaffected. > > If the log contents matter that much to you, you can stop and start > error logging when you change WHENEVER from STOP to CONTINUE and vice-versa. > > -- > Alan Denney yosemite_at_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