Support for Form Inheritance

Greeting

This is a question mainly directed at FR development guys.

I am trying to create a report heirarchy using form inheritance, but it appears that the TfrReport component does not honour form inheritance .. i.e. if I change the base class the change is not reflected, or updated in the sub-classes. ;)

I assume that this is due to the way the TfrReport is stored in the form resource. It would appear that the new form is basically a copy (in relation to the TfrReport component) rather than an inheritance. Is this something that is likely to change in FR3?

Form inheritance is a very useful feature when working with reports as it allows a base class to dictate the general layout (headers, footers, dimensions etc.) and common functionality of all reports.

Best regards

Steve

Comments

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.