Teechart & ReportPrinter Legal Issues
I want to use TeeChart in my reports.
As I don´t want to by the chart-component (since I only do simple line-charts) I
wanted to ask which packages do I need (at least) to successfully compile with
packages?
Which libraries do I need to include to my distribution of the software?
Is it legal to distribute my software with this libraries?
Regards,
Siegbert
--
Siegbert D. Waldner siegbert@waldner.info
As I don´t want to by the chart-component (since I only do simple line-charts) I
wanted to ask which packages do I need (at least) to successfully compile with
packages?
Which libraries do I need to include to my distribution of the software?
Is it legal to distribute my software with this libraries?
Regards,
Siegbert
--
Siegbert D. Waldner siegbert@waldner.info
This discussion has been closed.
Comments
distributed by the creators. If you go into the Component | Install
Packages dialog from Delphi, you will see a checkbox to build with runtime
packages. You'll see the runtime packages that you have installed into
Delphi. I think the TeeChart packages are like TeeUI, Tee and TeeDB. The
RB runtime packages are as follows:
ReportBuilder 6 and Delphi 6 package names shown below:
rbRCL66 Report Components
rbIDE66 Report Designer and supporting dialogs
rbDB66 Adds TDataset support for pipelines
rbCIDE66 Crosstab visual interface
rbCT66 Crosstab engine
rbRIDE66 RAP visual interface
rbRAP66 RAP code engine
rbDBDE66 BDE support for Data Access Development Environment
rbDAD66 DADE SQL generator
rbDIDE66 DADE visual interface
rbBDE66 BDE data access components
rbUSER66 Sample report components (checkbox)
rbTDBC66 Data-aware TeeChart wrapper
There are also packages for the DADE plug-ins, if the application is using
DADE. The proper package can be located in your installation of RB in the
..\RBuilder\Demos\End-User Databases directory.
Notice that the visual interfaces are broken out into separate packages.
This is useful if you don't provide the visual designer to the end user.
The engine behind the interface is all that is needed to be included in the
runtime packages list. For example, if you have built crosstab reports into
the application, but the end user will never design a report, then you'll
only need to include the crosstab engine (rbCT66) while excluding the
crosstab visual interface (rbCIDE66) package.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com