Report Explorer: Design, Preview, Email or Print?
Hi,
Delphi 6, RB 11.08 Enterprise.
I am using the Report Explorer to offer the user a list of reports to design
and print. If they want to print, preview or email the report, I'd like to
show some other options before printing, so that I can populate report
parameters before printing. If the user is going into the designer, I don't
want to do this.
I can't seem to find out how to determine if the user has elected to
print/preview the report? Is there an event or method on the Report
Explorer, Designer or Report components that will allow me to determine
this?
Thanks,
Jason.
--
Jason Sweby
Software Development Manager,
Carval Computing Limited, Plymouth, UK
Payroll - HR - T&A - Access Control
Delphi 6, RB 11.08 Enterprise.
I am using the Report Explorer to offer the user a list of reports to design
and print. If they want to print, preview or email the report, I'd like to
show some other options before printing, so that I can populate report
parameters before printing. If the user is going into the designer, I don't
want to do this.
I can't seem to find out how to determine if the user has elected to
print/preview the report? Is there an event or method on the Report
Explorer, Designer or Report components that will allow me to determine
this?
Thanks,
Jason.
--
Jason Sweby
Software Development Manager,
Carval Computing Limited, Plymouth, UK
Payroll - HR - T&A - Access Control
This discussion has been closed.
Comments
Report.OnInitializeParameters event can be used for what I need.
Is there another way, though, out of interest, to determine what action the
user has requested on a report selected via the Report Explorer?
Jason.
This rbWiki article shows how to detect whether the report is being
generated to the printer.
http://www.digital-metaphors.com/rbWiki/Output/Printer/Detecting_Whether_Report_Printed_to_Printer
Likewise to check whether a report is generating to file use the BeforePrint
event to check
If myReport.FileDevice <> nil then
None of the above applies specifically to the report explorer, they are just
general checks that the report can do. The Report Explorer knows about
Report, but the Report class does not know anything about ReportExplorer.
You could try creating a custom report explorer form that could monitor the
explorer activity.
--
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com