Thanks for the suggestion Alastair; however, what I am trying to do is incorporate the code within the report itself and avoid having to add code every time the report is called from multiple locations within the application. Having the code built into the report (pretty much like we do with forms) would make it a lot more portable.
Javier, Javier Valencia 913-915-3137 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alastair Burr Sent: Wednesday, September 24, 2008 5:42 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: Exiting a Report Javier, Is there a way you could amend the where clause so that no data can can be selected? For example: Your command might be written as:- SET VAR vWhere_Clause = 'WHERE Col IS NOT NULL' PRINT vReport &vWhere_Clause Then in your EEP:- IF [User] ... THEN SET VAR vWhere_Clause = 'WHERE Col IS NULL' ENDIF Then you could pop-up a nice message explaining why... Regards, Alastair. ----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, September 24, 2008 10:43 PM Subject: [RBASE-L] - Exiting a Report >I have a confidential report that it is called from many locations within >an > application. Rather than add code to check if the user has the permission > to > generate the report before the report is started, I would like to place > the > code in the report itself (Before generate). Is there a way to stop the > report with code from the "before generate" EEP? I have tried CLOSEWINDOW > but it does nothing and the report continues to execute...any ideas? > > Javier, > > Javier Valencia > 913-915-3137 > > ---------------------------------------------------------------------------- ---- No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.7.1/1688 - Release Date: 24/09/2008 06:29
