Hi, does RB support Client datasets? thanks -- Guillermo Castaño Acevedo Gerente de Sistemas - Grupo Millennium Ltda GuillermoC@GrupoMillennium.com www.GrupoMillennium.com Quid quid latine dictum sit, altum viditur
You can certainly use TClientDataSet with ReportBuilder:
TClientDataset --> TppDBPipeline --> TppReport
Therefore any end-user solution would have to utilize TClientDataSet.
However, the are some other factors here...
1. The Report Explorer has to work with TClientDataSet. This has not been tested and will likely have issues because the TClientDataSet will need to be refreshed when a folder or item is added.
2. The Query Tools, available from the Data tab of the report designer, build SQL statements for query based TDataSet descendants such as TQuery, TADOQuery, TIBQuery and other products. TClientDataSet is not SQL based - although they can be connected to a data provider that is SQL based. So the issue here is that for every TClientDataSet created by via DADE, there would need to be a SQL based Provider on the server side.
In addition the Query Tools rely on communication with a Session (or Connection) object to a get list of available tables, fields, etc.from the database.
Query Wizard <--> DADE Plug-in
DADE Plug-ins are sets of classes that implement the above functionality for various database connectivity products such as BDE, ADO, IB Express, Direct Oracle Access, etc.
Our current thinking is that implementing 3 tier End-User reporting would require creating a DADE plug-in for the client side functionality plus a Server side API to handle requests for creating data providers and returning the available tables and fields.
In a future version coul it be posible to have TClientDataset support going back through the dataset connected to the provider? ClientDataSet -> Provider -> DataSet? In that way you can go to the origin of the data. thanks
Comments
TClientDataset --> TppDBPipeline --> TppReport
Therefore any end-user solution would have to utilize TClientDataSet.
However, the are some other factors here...
1. The Report Explorer has to work with TClientDataSet. This has not been
tested and will likely have issues because the TClientDataSet will need to
be refreshed when a folder or item is added.
2. The Query Tools, available from the Data tab of the report designer,
build SQL statements for query based TDataSet descendants such as TQuery,
TADOQuery, TIBQuery and other products. TClientDataSet is not SQL based -
although they can be connected to a data provider that is SQL based. So the
issue here is that for every TClientDataSet created by via DADE, there would
need to be a SQL based Provider on the server side.
In addition the Query Tools rely on communication with a Session (or
Connection) object to a get list of available tables, fields, etc.from the
database.
Query Wizard <--> DADE Plug-in
DADE Plug-ins are sets of classes that implement the above functionality for
various database connectivity products such as BDE, ADO, IB Express,
Direct Oracle Access, etc.
Our current thinking is that implementing 3 tier End-User reporting would
require creating a DADE plug-in for the client side
functionality plus a Server side API to handle requests for creating data
providers and returning the available tables and fields.
Remote DataModule Client
----------------- -----------------
AppServer Query Wizard <--> daRemoteSession
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
through the dataset connected to the provider?
ClientDataSet -> Provider -> DataSet?
In that way you can go to the origin of the data.
thanks
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com