Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

Pipe.Visible and Loading from Template

edited August 2001 in General
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

Comments

  • edited August 2001
    Set the visibility of the datapipeline before the template is loaded.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited August 2001
    In article <8EAE82296ACCD311A039005004E0CAC004A1AD@DMSERVER>, Jim
  • edited August 2001
    The datapipeline property of the report wa schanged to a string property for
    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


  • edited August 2001
    In article <8EAE82296ACCD311A039005004E0CAC004A1DC@DMSERVER>, Jim Bennett
  • edited August 2001
    When you load a template, the template object creates a datapipeline list
    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


  • edited August 2001
    In article <8EAE82296ACCD311A039005004E0CAC004A1E9@DMSERVER>, Jim Bennett
This discussion has been closed.