Rbuilder 7.04 and IBObjects

Comments

• nardmoseley

  December 2004 edited December 2004

  
  I do not understand the question because you state "If I use the
  MasterDatapipeline and MasterFieldLinks in addition to
  master-detail setup of IBO native dataset, the results are printed
  correctly."
  
  What does that statement mean and what are trying to accomplish that is
  different?
  
  There are two types of data linking supported by ReportBuilder. Yo should
  use one or the other, but not both. See the following tech tip....
  
  
  ------------------------------------------------------
  Tech Tip: Linking SQL Queries for Master/Detail Data
  ------------------------------------------------------
  
  The following example shows two options for linking SQL queries to create a
  master/detail relationship.
  
  In this example, we are using Delphi's DBDemos data to create a
  Customer/Order relationship. Thus we wish to link the Orders detail to the
  Customer master.
  
  I. Delphi Query Linking
  ------------------------
  
  a. Set the detail TQuery.DataSource property to point to the master
  query's TDataSource component.
  
  b. In the SQL "Where" clause for the detail query use a ':' followed by
  the linking field name from the master:
  
  example
  select *
  from orders
  where orders.CustNo = :CustNo
  
  Now each time the master record position changes, the detail query will
  automatically be refreshed with the correct result set.
  
  
  II. RB DataPipeline Linking
  -----------------------------
  
  a. Set the detail DataPipeline.MasterDataPipeline to point to the master
  DataPipeline.
  
  b. Use the detail DataPipeline.MasterFieldLinks property to define the
  linking relationship
  
  c. In the SQL for the detail, retrieve all records and sort them by the
  linking master field:
  
  select *
  from Orders
  order by CustNo
  
  
  Notes:
  
  1. Using RB DataPipeline, each query is executed only a single time - thus
  performance is much faster.
  
  2. RB Professional and Enterprise Editions include a visual Data environment
  for creating SQL queries, defining linking relationships, and creating
  Ask-At-Runtime parameters. Using the RB tools you could create the above
  linked queries in about 10 seconds.
  
  
  --
  Tech Support mailto:support@digital-metaphors.com
  Digital Metaphors http://www.digital-metaphors.com
  
  
  
  
  --
  Nard Moseley
  Digital Metaphors Corporation
  www.digital-metaphors.com
  
  
  

  
  Best regards,
  
  Nard Moseley
  Digital Metaphors
  www.digital-metaphors.com
• rbuser

  December 2004 edited December 2004

  
  
• nardmoseley

  December 2004 edited December 2004

  
  If you want to send to us the source code the IBOPipeline we can look at it.
  We simply do not have the resources to develop what you are asking for.
  
  The decision to not descend from TDataSet is huge mistake. The Delphi
  TDataSet descendant architecture is provided to enable third party data
  access components to be seemlessly added to Delphi. There are probably
  50-100 third party data access component sets available that use this
  approach. That is the power of an object oriented architecture and it works
  very well. ReportBuilder's DBPipeline and DADE plug-in architecture
  leverages this architecture. And we have customer's just about every data
  access component out there.
  
  I do not understand why you cannot use the DBPipeline and IBO dataset
  descendant for your reports. That is the approach taken by our customers
  that use IBO. We have an IBO plug-in for our Query tools and it is used
  widely (if you have RB Professional or Enterprise, it is installed to
  RBuilder\Demos\EndUser Databases\Interbase\IBO).
  
  
  
  
  
  --
  Nard Moseley
  Digital Metaphors Corporation
  www.digital-metaphors.com
  
  
  

  
  Best regards,
  
  Nard Moseley
  Digital Metaphors
  www.digital-metaphors.com