Help with Teechart
We have just purchased the upgrade to RB 9.02 profrssional and are using
Delphi 7. We are using Teechart 5.03. When in design mode we can click on
the Teechart icon and drop a chart on the design form but we can't seem to
access any of the design capabilities. What are we missing? Do we have to
tell RB9.02 that we have version 5.03 of teechart? thanks, LL
Delphi 7. We are using Teechart 5.03. When in design mode we can click on
the Teechart icon and drop a chart on the design form but we can't seem to
access any of the design capabilities. What are we missing? Do we have to
tell RB9.02 that we have version 5.03 of teechart? thanks, LL
This discussion has been closed.
Comments
the message "class TppTeeChart not found" ... I checked my compnents and
Delphi 7 says I have Report Builder Components for Teechart 5.03 installed.
Does this happen at runtime and design time? At design time, check your
Delphi installed packages list for the "ReportBuilder TeeChart 5.03
Components" entery. If this is not checked you will need to check it. If
it is not there, you may need to recompile and install this package (located
in the \RBuilder\TeeChart\Tee503\... directory.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
it ... recompiled it (On the options prior to compile I checked design and
runtime) ... I can drop a TeeChartDB component on the design form but when
I click on it nothing happens. When I try to execute a report after design
I get the following message "Class TppTeeChart not found ... ignore the
error and continue?" also, I have a crosstab component on the same form and
when I click on it to change it nothing happens either. Although I can set
up a new crosstab report and the design capability shows up ... thanks, LL
This sounds like a corrupt install. Please follow the steps described below
to clean a corrupt install and then reinstall ReportBuilder. The fact that
it is saying TppTeeChart is not found means that for some reason ppChrt.pas
is not in your library path. You might want to check this. If you are
building with packages, you need to be sure the correct packages are being
accessed.
--------------------------------------------
Article: Cleaning up a Corrupt Installation
--------------------------------------------
If you have been advised by Digital Metaphors technical support that you may
have a corrupt installation, or if you are having difficulty installing,
compiling or running applications after a ReportBuilder install, then it may
be necessary to manually remove all ReportBuilder files from your system.
Corrupt installations usually result when you are installing over a previous
version of ReportBuilder which was not installed into the default directory,
which was recompiled from the source, or when ReportBuilder files were
manually moved from the default install location. Cleaning up a corrupt
installation, consists of locating all ReportBuilder related files, and
deleting them from your system. The first step is to use the uninstall
program to remove as much of ReportBuilder as possible.
Run the uninstall program
1. Exit Delphi, and all other applications. You should have no applications
running except the uninstall, otherwise you may lose some of your work.
2. Select Start | Settings | Control Panel from your Windows desktop.
3. Double-click the Add/Remove programs icon.
4. Locate the version of ReportBuilder you wish uninstall and double-click
it.
5. The first page of the Uninstall Wizard allows you to choose between an
Automatic or Custom uninstall. Choose Custom and click the Next button.
6. Click the Select All button, then the Next button. Repeat these steps
until you reach the last page of the wizard.
7. Click the Finish button. All of the items you selected will be removed
from the system.
8. After all the ReportBuilder files are removed, you may be prompted to
reboot the system. If this is the case, reboot the system.
Delete the ReportBuilder root directory (and all subdirectories)
1. Using the Windows Explorer, locate the ReportBuilder root directory. The
default directory is:
C:\Program Files\Borland\DelphiX\RBuilder
2. Once you have located this directory, inspect it. If you have any custom
work in this directory which you would like to keep, move it to another
directory.
3. Delete the ReportBuilder root directory.
Delete all remaining ReportBuilder files
1. Using the Windows Explorer, search the entire hard drive for all
occurrences of:
dclRB*.bpl
dclRB*.dcp
rb*.bpl
rb*.dcp
2. Delete any occurrences which correspond to the version you are removing.
All packages are named with the convention NN, where the first number
is the ReportBuilder version and the second number is the Delphi version.
Thus, a typical package name for Delphi 5 would be rbRCL45.bpl. The same
package for Delphi 4 would be: rbRCL44.bpl. Check Installing ReportBuilder
for a list of the packages associated with each version.
3. Using the Windows Explorer, search your hard drive for all occurrences
of:
pp*.*
da*.*
ra*.*
4. These are the prefixes used by individual ReportBuilder units. 'pp' is
used for ReportBuilder units, 'da' is used for DADE units, and 'ra' is used
for RAP units. Depending on which ReportBuilder you have (Standard,
Professional or Enterprise) you may not have all of these unit types.
Additional Notes
1. Never have Delphi running when installing ReportBuilder.
2. All ReportBuilder related files should be stored in the root directory
$(DELPHI)\RBuilder.
3. All ReportBuilder run-time packages should be stored in the
Windows\System directory.
4. You should never have ReportBuilder files in Delphi\Lib, Delphi\Bin or
Delphi\Projects\Bpl.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
5.03 ... completely uninstalled Report Builder 9.03 per your instructions
... installed version 7.04 of Teechart ... reinstalled version 9.03 of
Report Builder after completely deleting everything as you instructed ...
and we are still getting "Class TppTeeChart not found" once we try to
execute a report with a Teechart component installed ... what do we try
next? thanks, LL
1. If the issue happens at Delphi design-time, then check that RB TeeChart
related packages are installed.
2. If the issue happens at run-time, then you need to include the
appropriate units in the 'uses' clause of your app. Please see the following
article....
------------------------------------------------------------
Article: Controlling the End-User Environment
------------------------------------------------------------
If you are having difficulty getting the Data tab, the Calc tab, the
crosstab component or the TeeChart component to appear in your end-user
application, or you are trying to eliminate one of these capabilities from
the app, then this help topic is for you. The following paragraphs explain
the unit registration scheme used by ReportBuilder Pro, and how you can use
this scheme to get control over the feature set presented to your end-users.
In order to minimize the overhead in end-user reporting applications,
ReportBuilder employs a unit level registration scheme (similar to component
registration in Delphi.), whereby components and functionality can be added
at the discretion of the developer. In other words, you can control whether
the 'Data' workspace, the 'Calc' workspace or certain components appear in
your end-user reporting application simply by specifying or omitting certain
unit names from the uses clause of your main end-user reporting unit. The
advantage of this approach is that overhead associated with features such as
DADE, RAP or the crosstab component can be eliminated from your application
if you do not wish to pass these features along to the end-user. The
disadvantage is that you must manually add certain units to the uses clause
or these capabilities will not appear in the application.
In the end-user reporting demo project (located in the ...\RBuilder\Demos\1.
Report Explorer directory), the main unit is a form entitled myEURpt. At
the top of the unit for this form there is a series of conditional compiler
directives which, when enabled, cause certain functionality to appear in the
application. The conditional compiler directives in this unit are an
attempt to simplify the configuration of the demo application. However,
these directives do nothing more than add or omit certain unit names from
the uses clause of the form. The important thing to know is the unit names
and the functionality that including those unit names will provide. The
table below provides this information.
Unit Name Feature
---------- ---------------------------------------------------------------
daIDE DADE user-interface ('Data' tab)
raIDE RAP user-interface ('Calc tab)
ppCTDsgn User-interface for the configuration of the crosstab.
Normally the Crosstab Designer is displayed by accessing the
'Configure...' context menu option of a crosstab component.
If this unit is not included then this menu option is not
displayed.
myChkBox Checkbox components appear on the component palette when this unit
is
included. If you want to check out the source for these
components it
is in ...RBuilder Pro 4\Demos\RCL
ppChrtUI User-interface for editing charts. Normally the chart editor
is displayed by accessing the 'Edit...' context menu
option of a chart component.
If this unit is not included then this menu option is not
displayed.
ReportBuilder also uses the unit registration scheme to control which
database connectivity options are provided by the application. While
including the daDatMan unit will cause the 'Data' workspace to appear in the
Report Designer, that workspace will not be functional without a supporting
implementation. In ReportBuilder we call these implementations DADE
plug-ins. A DADE plug-in is nothing more than a Delphi unit which contains
the appropriate descendant class implementations needed by DADE to
communicate with a given database. Placing the data access implementation
in a separate unit gives us at least two benefits. One is that the user
interface is not tied to any specific database connectivity scheme. The
other is that the overhead associated with database support is limited to
the database connectivity products you are actually using. This means that
if you are using ADO to access your data, you need only include the daADO
unit in your uses clause and your application will use ADO only. Most
developers use DADE plug-ins to gain access to databases not supported by
the BDE, or to gain access to databases without the use of the BDE. The
following DADE plug-ins are provided with ReportBuilder Pro:
Unit Name Feature
---------- ----------
daDBBDE BDE support for the Query Wizard and Query Designer
daADO ADO support for the Query Wizard and Query Designer
daIBExpress Interbase Express support for the Query Wizard and Query
Designer.
daADS Advantage support.
daDOA Oracle support via the Direct Oracle Access components.
daODBC98 ODBC support via the ODBC98 components.
daIBO InterBase support via the InterBase Objects components.
daDBISAM DBISAM support.
You can use DADE plug-ins at Delphi design-time by generating a package
which contains one of these units and then installing it into Delphi. This
will allow you to use your preferred database product within the 'Data'
workspace at Delphi design-time. You can locate the various DADE plug-in
units in the ...\RBuilder\ Demos\EndUser Databases directories. A Delphi
package project has been provided for each DADE implementation so that you
can generate and install the plug-in at Delphi design-time. For more
information on how this can be done, see the ReadMe files in the EndUser
Databases directories.
Additional DADE Plug-ins are always being developed. Check the Digital
Metaphors web-site for the latest information (see the section
Friends:Data:DADE Plug-Ins.)
--
Tech Support mailto:support@digital-metaphors.com
Digital Metaphors http://www.digital-metaphors.com
--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
by removing the x in front of TeeChart ... when I try to recompile it and
reinstall it I get the following error [Fatal Error] MyEURpt.pas(81):
Internal error: U783 ... if I replace the check in front of TeeChart it
compiles and installs correctly ... what do you suggest? thanks, LL
Try doing a Project | Build rather than a compile. An internal error during
compilation means that the compiler itself has an error (i.e. a bug in the
compiler). This is not something that we have encountered.
Try doing the same for the RBuilder\Demos\Reports\Demo.dpr project (i.e.
there is an 'x' you can remove for TeeChart).
--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
under RB7 and in end the End User App I included ppChrt and ppChrtDP as you
did w/RB7. ... you have changed the TeeChart include for end-user apps in
RB9 to ppChrtUI instead ... I changed to ppChrtUI and it works fine now ...
thanks, LL