Re: Checking datatype of CHAR variable in 4GL

In article <p9evDCABX350Ew2j@smooth1.demon.co.uk>, David Williams <djw@smooth1.demon.co.uk> wrote: >>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 > > Don't you just hate the fact that there is no program info, no module > info and no line number info in that error message. Agreed there. I think the original reasoning is that the volume of generated code to track it would be extreme (combined with carrying that info down all the code levels to the bottom-level conversion routines). There are ways to narrow it down, such as logging "I'm here" messages upon entering each module in a debug context... > On on of our customer sites were are seeing ten's of these messages > no idea where it came from...even a debugging enviroment variable to > cause a core dunp would be better than nothing... > Whoa. These are NOT server messages -- the server will not accept data where conversion errors occur -- so I think this particular concern is invalid. >>Marco >>_______________________________________________________________________________ -- Alan Denney yosemite_at_netcom.com "My opinions may have changed, but not the fact that I am right." -- Ashleigh Brilliant