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

DBPipeline ppField question

edited October 2014 in General
DXE5, RBE-15.04

I just noticed something for the first time. When I drop a ppDBPipeline,
set its datasource, and double-click it to create/populate the ppFields,
as I click the individual data fields in the pipeline, all of the
DataType(s) are correct. At some point, however, (haven't determined the
point I'm afraid) all of the DataType information for all of the
pipelines is lost and therefore set to "dtNotKnown". I don't remember
this behavior being present in the past. At this point, I don't even
know what the ramifications might be for my application if I were to
simply ignore it.

What am I doing different in the IDE while working with forms/code that
might be causing this to occur.

Any/all ideas appreciated.

Comments

  • edited October 2014
    We are going to need more information about what might be causing this
    behavior. Has it had any effect on the functionality of your
    application? In my simple tests, the field type remains correctly set
    after the pipeline is connected to a report. I also tried running the
    report, saving and loading a template, and saving and loading the project.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited October 2014
    On 10/9/2014 3:27 PM, Nico Cizik (Digital Metaphors) wrote:

    Hi, Nico,

    Well, after a bit of experimentation, I discovered this: When initially
    setting up a new DBPipeline, I was opening (setting Active=true) the
    associated dataset before double-clicking the pipeline to populate the
    ppFields. I manually manage all opening and closing of datasets in my
    application so I never set the Open.. & CloseDataSource properties in
    any of my pipelines. However, the AutoCreateFields property defaults to
    true, which I've always just left as is. Evidently, when the datasource
    is open and the ppFields are auto-created initially, everything is fine.
    But, if I subsequently close the datasource via the Active property, and
    later double-click the pipeline, the AutoCreateFields property causes
    the pipeline to lose data type information.

    My solution was to leave AutoCreateFields turned on when initially
    setting up a new pipeline. Once the ppFields are created, I turn
    AutoCreateFields off. This way, regardless of the status of the
    datasource while in the IDE, the data type information doesn't get lost
    if I double-click the pipeline.

    Hope that makes some kind of sense. If you see that anything I'm doing
    could cause me future headaches, please let me know.

    Thanks!
This discussion has been closed.