You may also want to look at the DEBUG command... Javier, Javier Valencia, PE President Valencia Technology Group, L.L.C. 14315 S. Twilight Ln, Suite #14 Olathe, Kansas 66062-4578 Office (913)829-0888 Fax (913)649-2904 Cell (913)915-3137 ================================================ Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all system and destroy all copies. ======================================================
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Trinity Business Technologies Sent: Wednesday, January 07, 2004 5:10 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Additional Info On Error Handling Routine. Thanks Javier. I will give your suggestion a try. ----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Wednesday, January 07, 2004 5:04 PM Subject: [RBASE-L] - RE: Additional Info On Error Handling Routine. > I believe that TRACE does most of what you want. If not, you could trap the > error and cross reference it to a table that has error descriptions, there > was a thread a few months ago that discussed hot to create an error > description table; Oma Cox posted the code below to create the error message > table. At the beginning of each command file you can define a variable with > the file name, so you would have error code, error message, error > description and command file name that you can write to a file or to the > screen. There may be a MICRORIM_* or RBTI_* system variable that stores the > command file name that I am not aware; I can't think of simple way to get > the line number, although and again there may be a MICRORIM_* or RBTI_* > system variable that stores the line number. > Javier, > > -- errorcode1.rmd > -- Oma Cox, Office & Computer Services Inc. > -- 22 May 2003 > -- 22 May 2003 Rev 1 Published to Rbase List Server for 7.0 > > -- Load table with Error Codes and messages > set messages off > set error messages off > drop table errorcodes > drop table errormessages > CREATE temporary TABLE ErrorCodes (ErrorCode INTEGER, ErrorMessage text 100) > create temporary table ErrorMessages (ErrorMessage text 100) > > SET VAR vErrNum INTEGER = NULL > SET VAR vErrMess text 100 = NULL > SET VAR vErrNum = 0 > > WHILE vErrNum <= 5000 THEN > > SET VAR vErrNum = (.vErrNum + 1) > write 'Processing Error Code : ',.verrnum at 10,10 > OUTPUT ERR.dat > write '''' continue > SHOW ERROR vErrNum > OUTPUT SCREEN > > load errormessages from err.dat using errormessage > > select errormessage into verrmess from errormessages > > IF vErrMess IS NOT NULL AND vErrMess <> '-ERROR- Invalid message number > ( 565)' AND vErrMess <> '''' THEN > INSERT INTO ErrorCodes VALUES .vErrNum, .vErrMess > --else > --set var verrmess = 'NOT USED' > --INSERT INTO ErrorCodes VALUES .vErrNum, .vErrMess > ENDIF > > delete row from errormessages > > ENDWHILE > > CLE VAR vErrNum, vErrMess > > edit all from errorcodes > > RETURN > > > Javier Valencia, PE > President > Valencia Technology Group, L.L.C. > 14315 S. Twilight Ln, Suite #14 > Olathe, Kansas 66062-4578 > Office (913)829-0888 > Fax (913)649-2904 > Cell (913)915-3137 > ================================================ > Attention: > The information contained in this message and or attachments is intended > only for the person or entity to which it is addressed and may contain > confidential and/or privileged material. Any review, retransmission, > dissemination or other use of, or taking of any action in reliance upon, > this information by persons or entities other than the intended recipient > is prohibited. If you received this in error, please contact the sender and > delete the material from all system and destroy all copies. > ====================================================== > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Trinity > Business Technologies > Sent: Wednesday, January 07, 2004 4:40 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Additional Info On Error Handling Routine. > > Victor, > > I was looking for an error handling routine that will provide most of the > following information: > > * Error number. > * Error message. > * Error description. > * Command file in which error occurred. > * Line number at which the error occurred. > * Line of code that caused the error. > > Thanks, > > Rick Brown >
