Hello Doug,

Nice job.  This works pretty well, I appreciate it.  Still, it would be work
much better if explanatory text accompanied each error message.  I realize
that doesn't exist, but it would be most helpful.

Scott Sherer

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Hamilton
Sent: Tuesday, December 28, 2004 7:56 AM
To: RBG7-L Mailing List
Subject: [RBG7-L] - Re: error 2583

Paula, the code below will create a table called error_list with two 
columns, error_text and error_code.  The code was posted by Mike Ramsour 
in 1999:
"The bottom line is that this file creates a table and populates it with 
error codes and their associated text.  In its present form I imposed an 
upper limit of 5000 for the number of messages but I'm not sure how many
error codes there are.  Does anyone else?"

I just tested it in 7.1 and it ran ok.
Hope this helps - Thanks to Mike.
Doug

SET VAR vcntr INTEGER=0,verr_msg TEXT,vcol_val TEXT
CREATE TEMP TABLE error_list (error_text NOTE,error_code INT)
--
CREATE INDEX el_error_idx ON error_list (error_text)
--
SET MESSAGES OFF
SET ERROR MESSAGES OFF
--
WHILE vcntr < 5001 THEN
  OUTPUT errors.dat
  SHOW ERROR vcntr
  OUTPUT SCREEN
  LOAD error_list FROM errors.dat AS FORMATTED USING error_text 1 150
  SELECT error_text INTO vcol_val IND vcol_ind FROM error_list +
    WHERE COUNT=LAST
  IF vcol_val IS NOT NULL THEN
      UPDATE error_list SET error_code=.vcntr WHERE COUNT=LAST
      GOTO next_loop
    ELSE
      DELETE ROW FROM error_list WHERE COUNT=LAST
  ENDIF
  LABEL next_loop
  SET VAR vcntr=(.vcntr + 1)
ENDWHILE
--
QUIT

Paula Stuart wrote:

>Once again, I would like to comment that it would be VERY helpful to
>have an index of error messages and their meanings.  Nothing is so
>frustrating as to get an error message the meaning of which is lost on
>you.
>
>Paula Stuart
>  
>

Reply via email to