P
Peter Judge
Guest
Those errors will be coming from a FIND FIRST ConfigOption NO-ERROR. One couls make that case that every time you have code that checks for NO-ERROR that there’s a ASSIGN ERROR-STATUS:ERROR = FALSE after it, but I’ve rarely if ever seen that . The expected error ‘process’ for the OpenEdge.Net (and .Web and some others) classes is to use structured error handling (CATCH). Richard, where are you seeing/reading the ERROR-STATUS handle?
Continue reading...
Continue reading...