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

Print problem

edited October 2005 in General
My report uses the following DBPipelines

DBPipeline_Customer.datasource := datasource_customer

DBPipeline_Correspondance.datasource := datasource_Correspondance.

Datasource.Correspondance.Master := datasource_Customer

DBPipeline_Correspondance.RBCurrentRecord := ReCurrentRecord
DBPipeline_Customer.RBCurrentRecord := ReCurrentRecord

I create and save a new correspondance

The grid shows I am at the new correspondance record

On Print the table moves to the first record in the grid and prints that
record.

I move back to the newly created correspondance in the grid and click print
again and the correct report prints.

What am I doing wrong here please?

SteveW

Comments

  • edited October 2005
    Hi Steve,

    This question was answered/responded to in your previous post. Below was my
    reply. If you would like you may continue the conversation on this new
    thread.

    --

    Steve,

    I am confused about how you are linking your master detail relationship. If
    the Customer pipeline is the master and Correspondance pipeline is the
    detail, then why are you setting the Correspondance datasource as the master
    of the Customer pipeline. By definition this will not work correctly.
    Perhaps a clearer explaination of how your application is set up and what
    you expect to happen would help me understand this better.


    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited October 2005
    The post has not appeared at my office PC hence the new post. Sorry for the
    duplicate.


    I have now set the Customer_datasource as the Master for the
    Correspondance_datasource but still have the problem. The on print button
    contains:

    PPReport3.DeviceType := 'screen';
    PPReport3.PrinterSetup.PrinterName := 'Colour to Post';
    PPReport3.Print;

  • edited October 2005
    Hi Steve,

    As a test, comment all your event handler code out and re-run your report.
    If this helps the issue, periodically begin adding the event code back to
    isolate where the problem is being caused.

    --
    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited October 2005
    2 hours later. I had deleted the MasterDataPipeline between the
    coressponance & Master pipelines but I finally found that the field links
    had remained. Should this happen?

    Cheers

    Another day another dollar



This discussion has been closed.