Re: Checking datatype of CHAR variable in 4GL

John H. Frantz writes: > 3. I can't imagine anyone being interested in a log file growing at a > mad rate describing conversion error-codes that were handled by the > program. To say that the error log isn't really an error log but a > message log is kind of circumventing the issue. If you don't want the log file growing, include a "startlog" call with each switch of the "whenever any" directive: call startlog("my_log") whenever any error call my_error_func call startlog("/dev/null") whenever any error continue -- _____________________________________________________________________ | Colin McGrath cmm@trac3000.ueci.com | | Raytheon Engineers & Constructors, Inc. (215) 422-4144 | | Phila, PA, USA Standard Disclaimers Apply | |___________________________________________________________________|