Class TdaBDEQueryDataView not found
I'm using ReportBuilder 7.01 and Delphi 7 Emterprise
I'm working thru "Learning ReportBuilder". In the example of the exercises
one only drop a ppReportComponent on the form (no PipeLine components are
used), then go to ReportBuilder's design mode, click on the Data tab and
click on File | New ... Query wizard.
One one PC it's working fine but when I transfer the example source to
another PC, I get the error message:
Class TdaBDEQueryDataView not found.
Nowhere on the hard drive there's a daBDEQueryDataView.pas or a
daBDEQueryDataView.dcu file.
Regards,
Nols Smit
I'm working thru "Learning ReportBuilder". In the example of the exercises
one only drop a ppReportComponent on the form (no PipeLine components are
used), then go to ReportBuilder's design mode, click on the Data tab and
click on File | New ... Query wizard.
One one PC it's working fine but when I transfer the example source to
another PC, I get the error message:
Class TdaBDEQueryDataView not found.
Nowhere on the hard drive there's a daBDEQueryDataView.pas or a
daBDEQueryDataView.dcu file.
Regards,
Nols Smit
This discussion has been closed.
Comments
If you are working thru Learning ReportBuilder, then you should use the
included End-User Reporting Application. It can be downloaded from
http://www.digital-metaphors.com/LearnRB/LearnRB.exe
From your description it sounds like you have perhaps built your own end-usr
reporting solution?
To include BDE support for queries built with RB's Data designer, you need
to include daDBBDE in the 'uses' clause of your application. If it is an
end-user application, you need to also include daIDE. (See the article below
for more relevant information. This article is reposted from our Tech Tips
newsgroup).
For future reference, note that TdaBDEQueryDataView is a class, not a Delphi
unit. The class, TdaBDEQueryDataView, is located in the unit daDBBDE.pas (or
.dcu).
------------------------------------------------------------
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...' speed 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
ppChrt Adds standard non-data aware TeeChart component to component
palette.
If you have end-user reports containing the TppTeeChart
component, you
need to add this unit or the report will not be functional.
ppChrtDP Adds a data-aware TeeChart component to component palette.
This unit must be added if you have reports which contain
data-aware TeeCharts.
ppChrtDB Legacy unit which contains older version of data-aware TeeChart
component. If you have reports which contain TppDBTeeChart
components, you will need to add this unit to the uses
clause.
This unit does NOT work with the latest version of TeeChart
from TeeMach
and is provided only for backward compatibility with the
TeeChart component
provided with Delphi 3 and Delphi 4. If you have purchased
TeeChart or are
using Delphi 5, then you must use ppChrtDP.
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
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
Learning ReportBuilder is a stand alone application that you run. It does
not require Delphi at all. See the ReadMe.doc. From the Windows desktop
click the Start button, select Programs | Learn ReportBuilder, and click the
Learn ReportBuilder option. This will start Learning ReportBuilder.
Learning ReportBuilder is written for end-users. EndUsers do not typically
have Delphi installed or know what Delphi is.
The RBuilder\Developers Guide\RBuilder.pdf contains Delphi developer
oriented tutorials.
---------------------------------------------------------------
Article: Resources for Learning ReportBuilder
---------------------------------------------------------------
1. Learning ReportBuilder is a complete learning system designed to teach
end users how to build a range of reports, but it is also an excellent
resource for the developer who is just getting started with RB. Learning RB
includes a 125-page PDF file, a stand-alone application complete with a
database, and a help file. The PDF file contains a set of tutorials, which
can be completed using the provided application. Learning ReportBuilder can
be downloaded from:
http://www.digital-metaphors.com/LearnRB/LearnRB.exe
2. Developer's Guide
When you install RB, this guide is automatically installed into the
RBuilder\Developers Guide directory. It contains extensive conceptual
information and step by step tutorials which show how to construct reports
and reporting applications within the context of the Delphi IDE.
3. On-Line Help
Accessible via a single click of the F1 key from with the Delphi IDE, this
reference resource explains the classes, methods, properties and events
which make up the product. It is also an excellent source of information
regarding installation, troubleshooting and version history.
4. Examples
There are a large number of example reports and reporting applications
included with RB. These show how to accomplish some of the most frequently
requested types of reports. In total there are probably over 200 different
examples covering everything from crosstabs to full-blown end-user reporting
solutions. The RAP functionality included with ReportBuilder Enterprise has
a separate set of demos, tutorials, and help files.
5. news.digital-metaphors.com
The newsgroups are very active with both Digital Metaphors engineers, TeamDM
members (volunteers specially selected for their knowledge of RB and their
willingness to help) and RB developers all pitching in to answer questions
and help each other out. There is also a Tech Tips 'newsgroup' maintained
by DM Engineers which lists over 100 different articles outlining various
tips and techniques. Probably the easiest way to connect to the newsgroups
is to surf the digital metaphors site, go to the support section and click
the newsgroup of your choice:
http://digital-metaphors.com/rbuilder/support.html
6. support@digital-metaphors.com
When you are working on the really advanced stuff, and need an additional
point of view, we're always glad to help.
--
Tech Support mailto:support@digital-metaphors.com
Digital Metaphors http://www.digital-metaphors.com
--
Nard Moseley
Digital Metaphors
http://www.digital-metaphors.com
Best regards,
Nard Moseley
Digital Metaphors
www.digital-metaphors.com
to get the Data tab and then File | New.. | Query wizad
Regards,
Nols Smit
User Evnironment' chapter.
Add daDBBDE to your uses clause and recompile.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
Library tab I've added a library path to
C:\Program Files\Borland\Delphi7\RBuilder\Lib (here I found daDBBDE.dcu)
But ... I still get the error message: Class TdaBDEQueryDataView not found
and subsequently no Query Wizard and Query Designer.
Nols Smit