Lazarus
Programming => Packages and Libraries => LazReport => Topic started by: gelinp on April 09, 2016, 09:22:59 am
-
Hi,
I'm working with Lazarus 1.4.4 and FPC 3.0. Default Lazreport version display 0.9.9, but I've got a bug with master/detail like this one (http://forum.lazarus.freepascal.org/index.php/topic,24471.msg147571/topicseen.html)....
But the online help of the same component is a wiki page with a screencast displaying Lazreport 1.0.1 verion... (http://wiki.lazarus.freepascal.org/IDE_Window:_Package_Editor)
So my quesiton is : how to upgrade lazreport with lazarus stable version 1.4.4 ?
Thank you for your help.
-
Download(checkut) lazarus trunk: http://wiki.lazarus.freepascal.org/Getting_Lazarus#Getting_SVN_client. Copy LazReport from the Component folder to your local Lazarus\component folder(make a backup first). Rebuild Lazarus.
-
I downloaded with subversion last trunk for lazarus, so it's 1.7, but package lazarus report is always 0.9.9 !
Command to checkout lazarus was :
svn co http://svn.freepascal.org/svn/lazarus/trunk lazarus
Also I erased ~/.lazarus to rebuild a new clean environment only with this new version of lazarus.
So what can I do ?
-
I am working with Lazarus trunk most of the time, and LazReport is version 0.9.9 here too. So, I don't know where this screenshot comes from, maybe a private development repository? The version 0.9.9 bundled with Lazarus trunk is very alive, there were several updates in April and quite a lot in March.
-
@gelinp
I downloaded with subversion last trunk for lazarus, so it's 1.7, but package lazarus report is always 0.9.9 !
Although the version numbers is the same, the trunk lazreport is very different from the one came with Lazarus 1.4.4, as @wp already mentioned.
You should also give FortesReport a try, is much better then Lazreport. Is there any good reason to stay with Lazarus 1.4.4?
PS: I also find this: https://sourceforge.net/p/lazarus-ccr/svn/HEAD/tree/components/rx/trunk/LazReport/ , I have no idea what is the difference compared with trunk version.
-
But the online help of the same component is a wiki page with a screencast displaying Lazreport 1.0.1 verion... (http://wiki.lazarus.freepascal.org/IDE_Window:_Package_Editor)
This wiki page shows screenshot of package editor with LazControls 1.0.1, not Lazreport.
-
:-[
-
@gelinp
PS: I also find this: https://sourceforge.net/p/lazarus-ccr/svn/HEAD/tree/components/rx/trunk/LazReport/ , I have no idea what is the difference compared with trunk version.
Additional components (visual controls) for lazareport based on RxFPC components
-
I'll give a try to Forte report, but I would like to run lazreport because I spent few weeks to learning it... But here, I'm stopping because of a BUG "Access Denied" with Master/Detail datasets.
I dosn't take attention it was not lazreport 1.0.1 but Lazcontrols %) I'm a little tired... I'm now running Lazarus 1.7 with SVN trunk. It's a good think.
Thank you very much for your helps.
Have a good day !
-
I'll give a try to Forte report, but I would like to run lazreport because I spent few weeks to learning it... But here, I'm stopping because of a BUG "Access Denied" with Master/Detail datasets.
Without a demo application, nobody can help. Maybe there is a workaround or perhaps somebody can fix the issue(if any), but only after the error is confirmed. Can you create a test application?
-
For the record, the "Master/Detail" problem in LazReport was caused by a SqlDB bug on their bookmarks handling. Yep, it may be seen as LazReport bug and for this reason I have disabled by default the LazReport feature that could bring to surface this SqlDB bug in r52241.
-
For the record, the "Master/Detail" problem in LazReport was caused by a SqlDB bug on their bookmarks handling. Yep, it may be seen as LazReport bug and for this reason I have disabled by default the LazReport feature that could bring to surface this SqlDB bug in r52241.
Jesus, is there a bugreport about this bookmarks handling? I'm using bookmarks (not related to LazReport) and I would like to know if I can get unexpected behaviour.
Also, does this Lazreport problem appear with other libraries or only with SQLdb? If it works well with Zeos, then perhaps you should not just disable this feature.
-
But the online help of the same component is a wiki page with a screencast displaying Lazreport 1.0.1 verion... (http://wiki.lazarus.freepascal.org/IDE_Window:_Package_Editor)
That screenshot is of the LazControls package, not the LazReport package.
-
But the online help of the same component is a wiki page with a screencast displaying Lazreport 1.0.1 verion... (http://wiki.lazarus.freepascal.org/IDE_Window:_Package_Editor)
That screenshot is of the LazControls package, not the LazReport package.
Yes, as already noticed (http://forum.lazarus.freepascal.org/index.php/topic,32237.msg207688.html#msg207688 (http://forum.lazarus.freepascal.org/index.php/topic,32237.msg207688.html#msg207688)).
-
Yes, as already noticed
Sorry for the duplicate information. I replied before I read the whole thread.
-
For the record, the "Master/Detail" problem in LazReport was caused by a SqlDB bug on their bookmarks handling. Yep, it may be seen as LazReport bug and for this reason I have disabled by default the LazReport feature that could bring to surface this SqlDB bug in r52241.
Jesus, is there a bugreport about this bookmarks handling? I'm using bookmarks (not related to LazReport) and I would like to know if I can get unexpected behaviour.
See issue #26132 and issue #26146
Also, does this Lazreport problem appear with other libraries or only with SQLdb? If it works well with Zeos, then perhaps you should not just disable this feature.
The problem is triggered by one specific (and rare?) situation, if you have two datasets in master/detail relationship and before vising every record of master and detail datsets one saves both bookmarks with the purpose of restoring them back once processing have ended, then in this situation sqldb will fail. LazReport tried to do this in an attempt to preserve the cursors on the datasets it works with, in case the dataset were linked to dataset gui controls so the end user does not notice any visible change, now this chore is left to the programmer.
The reason why it fails and why it cannot be easily fixed in sqldb is explained in the comments of the bug reports.
-
See issue #26132 and issue #26146
I see, thank you.