[Progress Communities] [Progress OpenEdge ABL] Improve error messages so that something can actually be done with them

  • Thread starter Thread starter Stefan Drissen
  • Start date Start date
Status
Not open for further replies.
S

Stefan Drissen

Guest
Currently I'm investigating implementing unicode in our application using utf-8 for cpinternal and cpstream. One of our test beds is now reporting: Invalid character code found in data for codepage (12008) So instead of the current MO: a. go thru the needlessly annoying procedure of getting the debug-listing to find out which statement is throwing the error copy-lob) b. adding silly debug messages to indicate /which/ file. It would really improve efficiency if the message reported 'file 'x' invalid character code in data for codepage'. This kind of crippled error reporting can also be found in other places: define variable hq as handle. message hq:num-fields. Invalid handle. Not initialized or points to a deleted object. (3135) In this simple case its clear which handle is invalid, but in real software it would help if the message were 'hq: invalid handle.'.

Continue reading...
 
Status
Not open for further replies.
Back
Top