The ReportBuilder engine requires a bi-directional dataset, as it goes back and forth to handle group breaks and also for caching at the start of each page...
I was affraid to receive that answer since I know ReportBuilder behavior from our current use with it (V3.51! working great!).
Now, we are using DbExpress with MySql in a new product. We really like the way DbExpress make things simple (installation, performance etc.). Do you have any idea of how can we use DbExpress (MySql) + ReportBuilder afterall ? Do we really have to use other data access options than DbExpress to use ReportBuilder ?
Theoretically you should be able to install mySQL and connect via DBExpress. Then use TClientDataSet to access data. Of course, you'll need to enable local caching so that the data set can be bidirectional.
As far as I know using ClientDataSet in this way will result in bad performance (had nothing to do with ReportBuilder) since all the data is cached. especially with master - detail relationship.
Which data access components do you recomned to work well with mysql and report builder ?
It may result in bad performance, but I would certainly give it a try. It may work better than you expect.
As far a mySQL data access components, we don't have any recommendations. We've researched just enough to get TSQLClientDataSet and TSQLConnection working for Interbase (see the example in RBuilder\Demos\End User Database\Interbase\dbExpress) - this same basic config should work fine for mySQL...
Comments
version of RB by downloading the demo from www.digital-metaphors.com.
--
Cheers,
Alexander Kramnik
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
We tried the following:
MySqlDataBase <== TSqlConnection <== TSqlDataSet <== TDataSource <==
TDbPipeline <== TppReport
While tring to open the report we get the message: "Operation is not allowed
on a unidirectional dataset"
Any idea ?
Maayan.
"Alexander Kramnik (Digital Metaphors)" <alex@digital-metaphors.com> wrote
Good to hear from you again!
The ReportBuilder engine requires a bi-directional dataset, as it goes back
and forth to handle group breaks and also for caching at the start of each
page...
Cheers,
Tom Ollar
Digital Metaphors Corporation
http://www.digital-metaphors.com
info@digital-metaphors.com
Thanks for your reply.
I was affraid to receive that answer since I know ReportBuilder behavior
from our current use with it (V3.51! working great!).
Now, we are using DbExpress with MySql in a new product. We really like the
way DbExpress make things simple (installation, performance etc.).
Do you have any idea of how can we use DbExpress (MySql) + ReportBuilder
afterall ? Do we really have to use other data access options than DbExpress
to use ReportBuilder ?
Thanks,
Maayan.
Then use TClientDataSet to access data. Of course, you'll need to enable
local caching so that the data set can be bidirectional.
Cheers,
Tom Ollar
Digital Metaphors Corporation
http://www.digital-metaphors.com
info@digital-metaphors.com
As far as I know using ClientDataSet in this way will result in bad
performance (had nothing to do with ReportBuilder) since all the data is
cached. especially with master - detail relationship.
Which data access components do you recomned to work well with mysql and
report builder ?
Maayan
may work better than you expect.
As far a mySQL data access components, we don't have any recommendations.
We've researched just enough to get TSQLClientDataSet and TSQLConnection
working for Interbase (see the example in RBuilder\Demos\End User
Database\Interbase\dbExpress) - this same basic config should work fine for
mySQL...
Cheers,
Tom Ollar
Digital Metaphors Corporation
http://www.digital-metaphors.com
info@digital-metaphors.com