Guys:
Is here a way to disable the export to PDF, Word, Excel and email options in a report preview. Thank you.
Guys:
Is here a way to disable the export to PDF, Word, Excel and email options in a report preview. Thank you.
To my opinion, the only way to disable these options, is by changing the rpreview class yourself.
But why do want to disable them? These are very intereseting tools.
Regards,
Michel D.
Genk (Belgium)
I use : FiveWin for (x)Harbour v. 25.12 - Harbour 3.2.0 (May 2025) - xHarbour Builder (January 2020) - Bcc773
Export to Word/PDF/Excel and email options allow an employee to take out information outside the office.
That could be a reason.
Driessen:
Rao hit the mark. Confidential info & HIPAA protected data are the reasons. Program should not encourage end users to disseminate confidential data. Thank you.
Yo creo que el preview deberia tener variables como lExportToPDF, lExportToExcel, lExportToWord, lSendMail, etc. y tambien poder definir la manera en que actúe en cada caso, definiendo como actuar en cada caso: bSaveAsExcel, bSaveAsPDF, bSaveAsWord, bSendMail, etc.
Asi no habria necesidad de tocar el codigo fuente.
Saludos
I think the preview class should have variables as lExportToPDF, lExportToExcel, lExportToWord, lSendMail, etc.. and also to define how to act in each case, with bSaveAsExcel, bSaveAsPDF, bSaveAsWord, bSendMail, etc..
So there would be no need to touch the source code.
Regards
Hunter -
I'm wrestling with HIPAA security issues also. Please email me to... roger at leadersoft dot com ... if you'd be interested in discussing approaches to HIPAA compliance.
Thanks,
Right now we have these classdata bSaveAsExcel, bSaveAsPDF, bSaveAsWord, bMail (13.09).
Assigning dummy codeblocks ( eg { || nil | ) inhibit export of data. This is an immediate workaround without changing the source code.
But still the buttons are visible. I agree it is not elegant to display buttons which do not act.
I propose one class variable lCanExport ( default .t. ). When this is set to .f., all buttons for export to word/excel/pdf/mail will not be shown.
Invite comments.
I think we already know how to add additional user buttons with additional actions where needed.
Mr. Nages,
Maybe the solution could be to have a function where to define all parameters for rpreview():
WIndow style,
Menu style,
Button bar,
Options
etc
Thanks ![]()
nageswaragunupudi wrote:Right now we have these classdata bSaveAsExcel, bSaveAsPDF, bSaveAsWord, bMail (13.09).
Assigning dummy codeblocks ( eg { || nil | ) inhibit export of data. This is an immediate workaround without changing the source code.
nageswaragunupudi wrote:
But still the buttons are visible. I agree it is not elegant to display buttons which do not act.
I propose one class variable lCanExport ( default .t. ). When this is set to .f., all buttons for export to word/excel/pdf/mail will not be shown.
 RPrevUserBtns( { || .f. }, 2010,  )