Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Reuse V/S Extra Component

Status
Not open for further replies.

abhijitkolhatkar

Programmer
Dec 12, 2005
21
HK
Hi All,
Following is the scenario.
I am having a Sequential Section in my report which has 11 Report Sections.
Each Report Section reads SAME File.
Following are the two approaches to do that:
1. I thought it will be better to read the file once and store it in the buffer and use the buffered row again and again..
2. Straight Forward Approach: I can read the file again and again on all 11 report sections.
Following is a way reusability was implemented
In the 2nd Approach I can REUSE the DataStream component:
Following is how I can do that.

Step I:
Add one data stream component to one report section.

Step II:
In "Properties" for All ReportSections (AcReportSection), we can find "Slots" property group and there is a property associated for "DataStream".
Put the value for this property as
<ReportClassName>::<DataStreamName> (ReportClassName is name of ur ReportComponent, ur GRAND PARENT REPORT with AcReport class)

Now, My questions are:
1. Is it actually REUSABILITY?
2. I can implement this for HEADER FRAMES and other controls also whihc are common across multiple sections/sub-reports in same Main Report.
3. Does this kind of reusability has any advantages related to Performance etc?If yes why? If no why not?

Thanks in Advance!
Abhijit

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top