Pipe.Visible and Loading from Template
Hello!
I use Version 6.01 and have some troubles with this release. In this
version there must be changes to the loading of a Report. Most of my
Pipelines are set to Visible=False because the are loaded at the start
of the application and when I design a Report in another form I don't
want that a user see this pipelines already loaded. Before Designing I
switch Visible=True and after them i switch Visible=False.
But now it seams that the report will not be correctrly loaded when I
do this. This are giving endless pages because while loading the
pipeline are unvisible to the engine
Any comments or ideas?
Gruß aus den Bergen
Günter
I use Version 6.01 and have some troubles with this release. In this
version there must be changes to the loading of a Report. Most of my
Pipelines are set to Visible=False because the are loaded at the start
of the application and when I design a Report in another form I don't
want that a user see this pipelines already loaded. Before Designing I
switch Visible=True and after them i switch Visible=False.
But now it seams that the report will not be correctrly loaded when I
do this. This are giving endless pages because while loading the
pipeline are unvisible to the engine
Any comments or ideas?
Gruß aus den Bergen
Günter
This discussion has been closed.
Comments
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
RB6.0. So when you load a report, then I guess when you set the
datapipeline visible=True after the template has been loaded, the object
reference ins't set on the report for the now visible datapipeline. So when
the report template is streamed up, there is no reference set for a
nonvisible datapipeline. You'll just have to set the desired datapipline
visibility before the template is loaded.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
object which stores all of the visible datapipelines in the entire project.
This list is used to resolve the datapipeline string property such that the
object reference can be established to the datapipeline. What we could do
is add a property on the datapipeline list class which is used by the
template which could be set such that even non-visible datapipelines are
used when loading.
When you show the designer, you could only have the datapipelines set to
visible=True for that particular report.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com