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

Showing TdaDataManager

edited September 2002 in End User
Does anyone know how to show ONLY the TdaDataManager ??

Comments

  • edited September 2002
    DADE is tightly coupled to a report being attached to it. We do not have a
    demo of showing DADE by itself. You can launch the query designer
    standalone if you would like to create a query before launching the report
    as shown in this demo:

    http://www.digital-metaphors.com/tips/LaunchQueryDesignerViaCode.zip

    Cheers,

    Jim Bennett
    Digital Metaphors

  • edited September 2002
    But there is a possibility of showing it out, right? My approach is on the
    form, have a TppDesigner component (because TdaDataManager requies it),
    TPanel (as the TWinControl to hold the TdaDataManager or whatever it is
    trying to show). Then all I have to do is create the TdaDataManager with the
    information and I have my DADE section shown in TPanel (so I'm assuming).
    This is where I'm stuck. I think that I've done it but I don't know how to
    test it out. I have very little understanding on the Tda* package.

    Maybe if you could provide me with a more detail documentation on Tda
    package then I would be quite happy.


  • edited September 2002
    The Tda* classes are not documented as they were never intended to be used
    this way. Right now, the best documentation we can provide is the source
    itself. The best bet is going to be to figure out how we show DADE in the
    designer. First we register the design module
    ppRegisterDesignModule(TdaDataManager, 'TppDesignerWindow'). Then it is
    created with all the other modules in this call
    TppDesignerWindow.CreateDesignModules. I would start tracing there to see
    where the calls go in the creation process to lead you in the right
    direction. To see what the other classes do, place RBuilder\Source in your
    library path and drop breakpoints in the dataview create and check the call
    stack. This should highlight the classes involved in the creation of a
    dataview. Since we don't have any documentation other than the source, it is
    up to you to dig into it to try and figure it out. If you have any more
    questions, feel free to ask us.


    Cheers,

    Jim Bennett
    Digital Metaphors

  • edited September 2002
    Here is an example of extractng the TdaSQLObject and manipulating it.

    http://www.digital-metaphors.com/tips/ExtractSQLObject.zip

    Cheers,

    Jim Bennett
    Digital Metaphors

  • edited September 2002
    Ahh.. I've managed to bring the data module out as a separate portion
    without changing RB's code and/or hopefully logic. I hope I can send my
    attempt to you guys to review if my implementation could be safe or not. In
    the mean while I still require your asssistance in some area.

    My problem is to structure the DataModule into my database. The things that
    are needed is like number of queries, their link relationship, fields
    involved and tables. Getting fields is easy because I just have to get the
    ListView's list. So is the number od queries. To get the tables involved is
    abit tricky to me already. My approach is targetting on the
    TdaDataManager.DataViewWindows.ToolWindows : TdaDataViewToolWin. I have a
    hunch that the ToolWindow will store a TdaSQL object or it won't work what
    it is doing currently. My question is how to get it.
    My problem:
    To get TdaSQL object from TdaDataViewToolWin.

    I'm still working on the link part. I don't know where to focus on. I'll get
    to you once I have a direction where to approach, unless if you could
    provide me some direction to focus on.

    Thanks for the insight.


This discussion has been closed.