You can set the ERROR variable to whatever name you wish like: Set Error Variable vERR integer = 0
Then test for the value of vERR "immediately" after a command that you want to trap the error and test for non zero. If you know what the error number is in advance, you could test for comparison like: If vERR = nnnn where nnnn is the number to test against. In RBase Help: Syntax: SET ERROR VARIABLE varname ----- Original Message ----- From: "Bruce Chitiea" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, June 20, 2012 3:16 PM Subject: [RBASE-L] - Date Entry-Error Error Codes? All: RBE9.1_64 9.1.5.20510 Let's say I type a bad date: '06/31/2012' into a variable edit form control; or during a gateway import a funky date is processed. In the first instance, RBase blanks the field entry, returning the cursor to the first character position. In the second, I've not tried it yet. Either way, does R:Base throw a 'capture-able' error code available to exception handling routines? TIA Bruce --- RBASE-L ================================================ TO POST A MESSAGE TO ALL MEMBERS: Send a plain text email to [email protected] (Don't use any of these words as your Subject: INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH, REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP) ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: INTRO ================================================ TO UNSUBSCRIBE: Send a plain text email to [email protected] In the message SUBJECT, put just one word: UNSUBSCRIBE ================================================ TO SEARCH ARCHIVES: Send a plain text email to [email protected] In the message SUBJECT, put just one word: SEARCH-n (where n is the number of days). In the message body, place any text to search for. ================================================
