Is it possible to use Form-Inheritance for RB-Forms
Hi,
now I've some month of experience with RB creating new reports in new parts
of my projects.
Now the time is come to substitute old QR-Reports
i.e. to implement the taFullJustified-feature for generated letters.
But I'd like to use the same technique:
I've to generate several kinds of letters to our customers.
(1)
In a basic TForm (TfoqrBasis) I'd placed a TQuickRep-component and realised
some basic print features.
(2)
In a derived TForm-class (using TForm-inhertance-feature of Delphi) I've
made the basic letter features (address-field, date-field etc.)
TfoqrBasis --> TfoqrBasicLetter
(3)
From TfoqrBasicLetter I've derived department-specific TForms
TfoqrBasicLetter --> TfoqrDepartmetXYZ_Letter
(4)
From TfoqrDepartmetXYZ_Letter I've created the printable letter-Forms for
the required purposes.
In this way I benefit from all advantages of class inheritance. Every
improvement in parent-class are immediately realised in the childs.
In looking at the RB-generated forms I've some doubts to copy this tactic
for RB.
My two questions:
1. is this way possible in RB
2. if not, what is the recommended way.
--
Best regards
Dietmar Brueckmann
now I've some month of experience with RB creating new reports in new parts
of my projects.
Now the time is come to substitute old QR-Reports
i.e. to implement the taFullJustified-feature for generated letters.
But I'd like to use the same technique:
I've to generate several kinds of letters to our customers.
(1)
In a basic TForm (TfoqrBasis) I'd placed a TQuickRep-component and realised
some basic print features.
(2)
In a derived TForm-class (using TForm-inhertance-feature of Delphi) I've
made the basic letter features (address-field, date-field etc.)
TfoqrBasis --> TfoqrBasicLetter
(3)
From TfoqrBasicLetter I've derived department-specific TForms
TfoqrBasicLetter --> TfoqrDepartmetXYZ_Letter
(4)
From TfoqrDepartmetXYZ_Letter I've created the printable letter-Forms for
the required purposes.
In this way I benefit from all advantages of class inheritance. Every
improvement in parent-class are immediately realised in the childs.
In looking at the RB-generated forms I've some doubts to copy this tactic
for RB.
My two questions:
1. is this way possible in RB
2. if not, what is the recommended way.
--
Best regards
Dietmar Brueckmann
This discussion has been closed.
Comments
You can use form inheritance with some limitation:
1. Do not place the DataPipeline components on an ancestor. Due to the
DataPipeline.AutoCreateFields feature, form inheritance does not work.
2. Do not use report templates (i.e. .rtm files or database templates)
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com