Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Garbage in 'type' field of Data Dictionary

edited March 2004 in General
I am using Delphi 7 + ReportBuilder 7.03. When I add a data dictionary as
per the ReportBuilder Developers Guide, "Adding Data Dictionary Support to
the End-User Application", and I click on the Data tab of the Report
designer, I get garbage charactors in the type field of the Dataview. This
is on my database. When I use the tutorial's database the data fields are
blank.What up?
- jimc

Comments

  • edited March 2004
    Hi Jim,

    Which database/connectivity are you using? Do you get this behavior when
    running any of the End-User demo apps? If you stop using the
    DataDictionary, does the problem go away? When accessing a dataset,
    ReportBuilder tries to match the database datatypes with its own datatype
    definitions. If it cannot resolve one of these types, it usually will come
    up blank.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited April 2004
    Nico:
    1. I am using the standard Paradox BDE database that comes with Delphi.
    2. When I define a query to the DBDEMOS database (the one with 'customer'
    table) the type field is blank. When I define a query to my tables the type
    field is garbage charactors (something like '$!!#$$#$!!'), and they are the
    same garbage charactors whether its an integer type or a boolean or a
    varchar or whatever.
    3. If I stop using the Data Dictionary (by setting the UseDataDictionary
    property to false in the TppDesigner) and re-define the same data query, the
    type fields are correctly identified as integer, varchar, etc.
    - jimc

  • edited April 2004
    Nico
    I found it.

    In Developer's Guide 2nd edition (p.324) the instruction say to make the
    Datatype field a char of size 1 (varchar(1)). It allowed only the first
    character of the real datatype in the fields table. It was a 'd' in all
    cases.

    This was corrected in the 3rd edition.It should be of size 60 (varchar(60)).
    Thank you.

    - jimc


This discussion has been closed.