L
Laura Stern
Guest
But seriously, you are missing my point. I was already agreeing with you that the "ERROR" was coming from the EOF. In fact, I even agree that this is a bug! But this is easily fixed, not by the work-around you showed, but by simply removing the check for ERROR-STATUS:ERROR outside of the REPEAT block. The value in the MESSAGE inside the REPEAT block always says the correct thing. The last time, when you get EOF, while it sets ERROR-STATUS:ERROR, it also kicks you out of the block. So you never get to that MESSAGE statement (in this case) that looks at it. So to repeat what I said above, you should check for an error immediately after using NO-ERROR. If you do that, it works as expected. Immediately, means immediately - the next line. Not after the END statement following. I have no objection to you logging a bug, but I'm trying to be honest with you. I think that it will get low priority. 1. It is a behavior change which is always problematic for us. 2. There is a simple "work-around", which isn't even a work-around, it is just coding correctly based on the way that NO-ERROR is designed to work.
Continue reading...
Continue reading...