New Blog Post: RESTful Reporting

TraCodeModule Not Found

edited September 2002 in Server
I'm getting a server error -

"Server Error: Processing request for report "
"EReportLoadFromDatabaseError, Class TraCodeModule not found"

This report previews fine via the report explorer but fails when I call it
from a client connection in Delphi.

What am I missing and from where?


RB7 Server using DOA / Oracle Database / Delphi 6


  • edited September 2002

    Add raCodMod to the 'uses' clause of the main form of the application.That
    will link support for RAP into your application.

    Check out the article below for related information.

    Article: Including Required Classes in a Server Application

    The report server application that you build must include all classes
    necessary to execute each report. To minize overhead 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
    DADE, RAP, or certain components are included in your server application
    simply by specifying or omitting certain unit names from the uses clause of
    your main form. 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. The disadvantage is that you must manually add
    certain units to the uses clause or these capabilities will not appear in
    the application.

    Unit Name Feature
    ---------- -------------------------------------------------------------
    daDataModule DADE run-time support

    raCodMod RAP run-time support

    ppCTMain Crosstab run-time support

    ppChrt Non-data aware TeeChart classes.

    ppChrtDP Data-aware TeeChart classes

    myChkBox Checkbox classes

    ReportBuilder also uses the unit registration scheme to control which
    database connectivity options are provided by the application. 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

    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

    daADS Advantage support.

    daDOA Oracle support via the Direct Oracle Access components.

    daIBO InterBase support via the InterBase Objects components.

    daDBISAM DBISAM support.

    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
    Digital Metaphors

    Best regards,

    Nard Moseley
    Digital Metaphors
This discussion has been closed.