Hi,
If you want to use the reportcontrol the best thing you can do is to disable the
// oReport:SetCustomDraw( xtpCustomBeforeDrawRow )
This slows down the reportcontrol. If this is disabled, the speed is very good, and the control can be used with big tables.
With the definition of a header array and putting the data in an array, you can create with a minimum of effort a very functional report control.
Speed of cjReportControl
Re: Speed of cjReportControl
As I understand the docs, this would conflict with the "Virtual Mode", which is needed for large datasets. ![Confused :?](./images/smilies/icon/confused.gif)
![Confused :?](./images/smilies/icon/confused.gif)
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: Speed of cjReportControl
Hi Tom,
I tested with a report of 15.000 lines, and it works without problem.
I will use the control to offer an easy way for subtotaling, moving columns, and printing the way the user wants it. The user can drag and drop columns, change order, change subtotalling, ...
I don't want to use this as a browse on large datasets.
I tested with a report of 15.000 lines, and it works without problem.
I will use the control to offer an easy way for subtotaling, moving columns, and printing the way the user wants it. The user can drag and drop columns, change order, change subtotalling, ...
I don't want to use this as a browse on large datasets.