F
Fernando Souza
Guest
As Frank pointed out, make sure you don't have anything set that would suppress the messages from being logged. _msg() will return the message that was last issued, but there is no context so it could had been issued before you ran the code (just fyi). But the fact that you do see the error number means that it did get issued, but if you don't see the message in the log file, that indicates that there is something probably suppressing it. With all that said, that message will not cause a STOP condition. Generally, the STOP condition comes with an error message, but sometimes it might not, which is not desired. Since you don't know where it is coming from, you may want to turn on the 4GLTrace log entry with logging level 3. That will record the return from any procedure/function and will have a STOP tag at the end of the entry when a STOP condition is being raised which can help you narrow down the piece of code where the STOP is being raised. You would see something like this in the log file: 3 4GL 4GLTRACE Return from i-proc [prog1.p] STOP
Continue reading...
Continue reading...