delphi code (2008-8-19)

This is easy Dephi code to write, but the coder that takes the project must be skilled and be able to write crystal clear code. An existing main application (that you won't see) must produce several new reports: all the ones shown in the attached PDF. I have started writing the code using one TComponent per each report, all inheriting from class TAbsRep (in unit [login to view URL]) . Data is passed from the main application by class fields (see TAbsRep1 in [login to view URL]) and /or in lists (see TAbsRep3 in [login to view URL] ). Each class has the method function Test:boolean that will 1. fill fields and lists with data taken from the PDF file 2. call the Execute function, that produces the report There is no database to query. I am very busy with different work, so I am asking somebody to complete the work (which is easy but time-consuming) along the style shown in the attached code. You should see that the code is well structured and details are hidden. Whenever possible, the code is inherited. Somebody who browses the code for maintenance should be able to quickly understand what happens even without comments, as procedures have self-explaining names. I'd like you to produce as nice code as I would...or even better (I am always ready to learn from capable people) In order to avoid surprises re the work, the coder will provide each report as soon as completed. Online help is provided at any time via GTalk (preferred) or RAC chat. If I leave for a business trip, I will still be avaiable via RAC messages. The final code must compile in Delphi 5. Trying the attached code, you will need control TProfgrid, which is avaiable in trial version at [login to view URL] . If you have problems downloading from RAC, the attachment will be avaiable for some days also at the following address: [login to view URL] Please note that in some points my code must be completed (e.g. procedure procedure [login to view URL] in tur_fy). Also the code that formats the recurring columns should be transformed into method(s) of the common ancestor. This way, it will be easy to change in the future if so needed