Good thought Larry but the report is very basic, no EEPs at all. In this case the "where clause" fails so I don't think the logic inside the report would even execute. If error messages are set to on, the 2038 error pops up on the screen but it does not set error variable.
Your rStatus suggestion is a good one. That should eliminate the overhead of the pre-count. John From: [email protected] [mailto:[email protected]] On Behalf Of Lawrence Lustig Sent: Friday, July 17, 2009 3:25 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Using the ERROR VARIABLE << However, does anyone know why the error variable is not setting. It does set if the select fails. But if the print command fails it does not. >> Do you have any EEP code in the report at all (for example, in BEFORE GENERATE). If so, those commands could possibly be resetting the error variable. Also, RBTI may have removed the ability of PRINT to set the error variable because of this EEP issue. You can pre-count for rows if you want, or add a variable or EEP code in your report to set rStatus = 'COMPLETE'. Then do: SET VAR rStatus = 'FAILED' PRINT. . . IF rStatus = 'FAILED' THEN . . . ENDIF -- Larry
