Re: What are error messages for?
The way it used to be done was to generate an error number and then feed the number to an "explanation" routine that documented it for the end-user. The routine needed (and I saw this happen) a subroutine that reported "The application error message is an error" when the error number did not match anything.
Biting the hand that feeds IT
