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

Slow initialization

edited March 2003 in DADE
Hi

I have some problem with the system. We have more than 1000 tables in our
database. It takes more than a minute to start up the designer for the first
time. I have found out the corresponding codepiece:

You have a routine:

procedure TdaMetaData.GetTablesFromSession(aTables: TList);

In this procedure you open a dataset for all the tables just for getting the
maximal namelength. I understand that you need to know that data, but if I
comment this part out the startup time will be not noticable. I do not want
to write into your code. Do you know any other mean to overcome this
slowness?

thanks

Ferenc Lendvai

Comments

  • edited March 2003
    ReportBuilder's data access environment needs to know the available table
    names in order to support the query tools. You could try using the Data
    Dictionary component to define the table/field/join names. RB will use the
    data dictionary to get the table names instead of firing a query to get them
    from the database meta data directly. 1000 records should be able to be
    returned fairly quickly using the data dictionary table dataset on the form.
    There are demos in our installation that show how to use the data
    dictionary. There are also help topics on this and descriptions in the
    Developer's Guide pdf of the installation.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.