MasterDataPipeline setting lost
I have defined a master detail relationship between two ppDBPipeline
objects.
Every time my project is opened, the MasterDataPipeline setting is missing.
The project and units have all been saved before closing.
This is quite frustrating, especially for the customers where the report is
not working as supposed if this is forgotten at compile time...
Hope that some of you out there can help...
RB 10.06 Enterprice, D2007, WinXP Prof SP 2
objects.
Every time my project is opened, the MasterDataPipeline setting is missing.
The project and units have all been saved before closing.
This is quite frustrating, especially for the customers where the report is
not working as supposed if this is forgotten at compile time...
Hope that some of you out there can help...
RB 10.06 Enterprice, D2007, WinXP Prof SP 2
This discussion has been closed.
Comments
Are you setting the MasterDataPipeline property at designtime and loosing it
at runtime? Are you able to recreate this with a simple example? If not,
there must be something in your code that is clearing out this property. I
would suggest tracing through your application's code keeping an eye on that
property to find out exactly when it looses its value.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Sorry for being unclear.
This is how I can reproduce:
Sett the property at designtime.
Save my project.
Close Delphi.
Open Delphi.
Open Project.
Now the setting is lost.
Petter
In my testing I was unable to recreate this issue. Below are the following
steps I took. Note that I am using RB 10.07. Although we have never heard
of this issue, I would recommend updating your version to the latest.
Create a project with two TQuery, two TDataSource, two TppDBPipeline, and
one TppReport and connect each of them accordingly.
Save and close the project.
Open the project, assign the MasterDataPipeline property of the detail
pipeline.
Assign a field link for the detail pipeline.
Save and close the project and Delphi.
Open Delphi and the project.
All properties are still valid.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
FTR: I've seen this and reported it a few years ago. I created a demo and
you could not reproduce it at that time either.
Edward Dressel
Team DM
I will upgrade to the latest version, but this problem has been persistant
over several versions.
Is this the recomended way to produce a master/detail report?
If so, I would appreciate if you could provide some help on trying to track
down this problem...
Regards
Petter Topp
This may have something to do with the order each component was created in
your app. Please try to recreate this issue with a new application noting
the order you create (place) each component on the form. Let me know the
exact steps you take to recreate the issue from the time you create the new
Delphi VCL application.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I have done this in several ways now and every one come up with the same
result - MasterDataPipeline missing.
Here are the two of the ways I tried:
A
1. From the menu, new vcl forms app.
2. Added a datamodule.
3. Copied the objects in question (Two queries, two datasources, two
datapipelines) from my live project.
4. Saved the project.
5. Closed the project.
6. Opened the project.
7. MasterDataPipeline missing.
B
1. From the menu, new vcl forms app.
2. Added a datamodule.
3. Added a Dbisam database object, a Dbisam Session, set the properties.
4. Added two Dbisam queries, renamed them, assigned these to the database,
added SQL Strings.
5. Added two Datasources, renamed them, assigned these to the Queries.
6. Added two Datapipelines, renamed them, asigned these to the datasources,
set up the masterdetail relationship.
4. Saved the project.
5. Closed the project.
6. Opened the project.
7. MasterDataPipeline missing.
Thanks for the additional information. Currently all pipeline properties
are resolved inside the Report object. In all of my tests, I had a report
object on the form/datamodule so I could not recreate the issue. Since you
have your report object separate from the datapipelines, they're properties
are not being resolved when the datamodule is loaded. We will fix this for
a later release.
As a work-around, you can add an empty report object to your datamodule.
This "dummy" report will allow the pipelines in the datamodule to keep their
references once they are loaded.
--
Regards,
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
I have added a dummy report to my datamodule, and this solved the problem.
Petter