Recompile packages

rbuser

Hello,

I'm using reportbuilder 10 enterprise and also DevExpress skinning.
De print dialog of reportbuilder is not correctly skinned when shown in a
skinned application.
How can I modify the screen and recompile the packages so the changes are
compiled in the executable?

Thx,
Bernaert Dominique

nicocizik

Hi Bernaert,

There should be no need to recompile the RB packages unless you are building
and deploying your application with packages. Take a look at the article
below on replacing dialogs in ReportBuilder.

------------------------------------------------------------
Tech Tip: Replacing Built-in Dialogs/Forms in ReportBuilder
------------------------------------------------------------

ReportBuilder has an open architecture for replacing any of the built-in
dialogs. You can replace any of the built-in dialogs by creating a new form
that inherits from an abstract ancestor and then registering it as the new
built-in dialog.

For example to replace ReportBuilder's print dialog you could

1. Create a new Print dialog by renaming ReportBuilder's default print
dialog, then doing a SaveAs to save it under another unit name.

The default dialog resides in RBuilder\Source\ppPDlg.pas and the form is
called ppPrintDialog. You should assign your form a unique name, for
example, myPrintDlg, and save the unit to another name. Also save the unit
to the directory where your other forms are stored (not RBuilder\Source).

2. Make desired changes.

You will notice that the print dialog inherits from an ancestor
TppCustomPrintDialog - this ancestor resides in ppForms.pas (where all the
abstract ancestor forms for ReportBuilder are defined).

3. Register the new form.

Declare an initializtion section at the bottom of the unit:

initialization

ppRegisterForm(TppCustomPrintDialog, TMyPrintDialog);


4. Add the new unit to your project and compile.

Now your preview dialog should be automatically created and destroyed by
ReportBuilder. The two page preview dialog in the
RBuilder\Demos\Reports\Demo.dpro was created this same way. The only
difference is the ppRegisterForm call is in then OnClick event of the
button.


--
Regards,

Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com