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

Replacing TdaSQL functionality

edited January 2007 in General
I want to force (a descendant of) TdaSQL to use the SQL that I give it,
without it generating the SQL.

How can I do that without modifying daSQL.pas by changing
TdaSQL.FSQLText and TdaSQL.SetSQLText() to protected and setting
TdaSQL.SetSQLText() to virtual?

Note that I also want to retain the ability to join queries on the Data
tab. So using "SQL as text" seems to be out, unless I am allowed to
explicity add field information that the Data tab can use (in fact, this
would be my preferred option).



--- posted by geoForum on http://delphi.newswhat.com

Comments

  • edited January 2007

    I think what you are asking is 'How can edit the SQL directly and still have
    the visual linking (and autosearch) support?'

    That is something we would like to add to a future release. It is hard to
    predict what issues you will encounter trying to implement this type of
    functionality. It will require the review the source code to
    TdaQueryDataView and TdaSQL. Probably try to create a custom QueryDataView
    descendant. The architecture is open to creating and registering descendants
    of TdaCustomDataView or TdaQueryDataView - and you can deing associated
    custom Data Designer classes.

    - You might check out TdaQueryDataView.IsLinkable and IsLinkableAsMaster for
    starters.

    - For the DataPipeline linking logic to work, the detail data needs to be
    sorted on the linking field(s)




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

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.