Modifying reports with componsnts that link to evetns in the code
Hi
I need to give my end users the ability to modify the reports in their
directories. the problem is that some of these reports link to specific
events (ongettext) in the code in certain forms. When I load the report in
another form to edit the design then it complains about the missing events.
Is it possible to get the load to ignore these so that the end users can
adjust the size and position of components and still leave the events
linked.
Paul
I need to give my end users the ability to modify the reports in their
directories. the problem is that some of these reports link to specific
events (ongettext) in the code in certain forms. When I load the report in
another form to edit the design then it complains about the missing events.
Is it possible to get the load to ignore these so that the end users can
adjust the size and position of components and still leave the events
linked.
Paul
This discussion has been closed.
Comments
- best solution is to use the run-time Pascal environment (RAP) that is
included with ReportBuilder Enterprise to code the event-handlers. That way,
the report code is stored as part of the report definition
- the other solution is make your event-handler methods published methods of
the of the form that contains the TppDesigner and TppReport components. This
will get messy if you have many reports and you will probably need to rename
some of the event-handler methods to avoid naming conflicts
ReportBuilder leverages Delphi's built-in support for component peristence
(streaming). The values of published properties are saved as part of the
report defintion and in the case of event properties, the name of the
event-handler method is saved. When the report loads, the Delphi streaming
system looks to Report.Owner for a published method with the same name.
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com