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

TdnxSession.GetDatbaseForName...

edited January 2009 in General
I'm converting older Flashfiler reports to Nexus. I have all of the components, including the NxDatabaseMapper
configured as usual, and I have altered a test report using the "Edit RB Templates as Text" utility. I have confirmed
that I am altering and saving the changes via this utility.

However, when I try to "run" this altered report, (double-clicking in the IDE) it comes up fine in the Designer, but
when I either try to preview or otherwise work with the tables on the data tab, I get the following:

"TdnxSession.GetDatbaseForName: No TnxDatabase object found for the specified name, NxDatabase1."

Additionally, (and of course it is probably related), I am not able to define from the dropdown a database name from the
database settings screen on the data tab in the Designer.

Thanks for any hints anyone can provide...I'm pulling my hair out trying to find this bug!!!

John

Comments

  • edited January 2009
    Sorry,

    Report Builder, 10.2, Delphi 2005

    Nexus 2.6

    John
  • edited January 2009


    The form/datamodule that contains the Report and Designer components needs
    to also contain a TnxDatabase component.

    When the DADE plug-in for Nexus is installed it will register a new
    SessionType, NexusDBSession.

    Configure the Designer.DataSettings.SessionType to be NexusDBSession and the
    DatabaseName to be the name of the TnxDatabase mentioned above.

    When you create QueryDataViews, the DataSettings will be saved as part of
    the query. When the report is later loaded, the DatabaseName will be
    resolved to the TnxDatabase component. If no such component exists, then you
    will receive the error message that you are reporting here.


    --
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited January 2009
    Nard,

    Thanks so much!

    Moving the report, data dictionary, explorer, and designer to the actual datamodule corrected the problem.

    Thanks again!

    John
This discussion has been closed.