Home Component Writing
New Blog Posts: Merging Reports - Part 1 and Part 2

Changing class inheritance

edited December 2015 in Component Writing
Hi,

in Version 5.56 we used TSpecialRichtext=class((TppDBRichText), as the
texts are stored statically in our DB.
After my investigations now I have to they that this decision of our
system-architecture was and is wrong.
Normally it should be TSpecialRichtext=class((TppRichText).
I can made these code changes, but I do not know what happens with our
reports when migratin from 5.56 to 16.03 including this change?

Will reports containing old TSpecialRichtext still work with the new
implementation. I assume, but can anyone confirm?

Tia Carsten

Comments

  • edited December 2015
    Hi Carsten,

    In the current version of ReportBuilder TppDBRichText and TppRichText
    both descend from the TppCustomRichText class. If you take a look at
    the TppRichText and TppDBRichText classes you will see that they are
    fairly minimal with most of the processing and features being in the
    ancestor.

    I suggest checking your code to be sure no features exclusive to
    DBRichText are being used. If not, you should not have an issue
    descending from TppRichText.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited December 2015
    Refactored component to TPPRichtext, works now as before!

    Nico Cizik (Digital Metaphors) machte diesen Vorschlag :
This discussion has been closed.