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

ReportBuilder Update problem from Version 5.55 to 6.03

edited July 2002 in General
I have the following problem when I have updated from ReportBuilder 5.55
to version 6.03:

We have many customers that are using at this moment our application
written in Delphi 5 that uses ReportBuilder v 5.55 to print their reports.
We have now version 6.03, and when we update the application and send the
.EXE file to our customers, they get the following error: "Error reading
.DATAPIPELINENAME: Property does not exist". Customers have report
templates saved to disk, and they got this message when they try to print
these reports.
- Must I send them also report files? (Editing templates and saving them
later, in order to get this new property)
- Is there any way to avoid this? (Think that there are hundreds of
customers with many different reports, personalized for each one).

Thank you in advance.

Comments

  • edited July 2002
    We would normally install 5.55 to test this, but unfortunately, last week we
    lost all of our installation programs from our network and we are currently
    attempting to recover them from backups but have been unable to recover them
    at this time. The 5.55 -> 6.03 conversion process we have in 6.03 should
    work correctly and your users should not get this error. We've seen this
    error before but haven't researched the issue to resolve it completely. One
    thing that you can check is your environment settings which may have RB 5.55
    source/dcus in it.


    Cheers,

    Jim Bennett
    Digital Metaphors Corp.

  • edited July 2002
    Can you send us the report- we can run it here in 6.03 to see why it isn't
    converting. Please send it to support@digital-metaphors.com


    Cheers,

    Jim Bennett
    Digital Metaphors Corp.

  • edited July 2002


    Hello, Jim.

    Well, I think it will be a bit difficult to send you one of the reports
    from version 5.55, because I'll have to send you database file (Interbase)
    and main program. It's not a standalone report you can run without the
    application. But I propose you a possible way to test the error I get in
    conversion: that is, make a simple report with version 5.55 in a single
    computer, update it to version 6.03 and try to run the same report. Yes, I
    know it?s obvious, but I think this is the easiest way to test this. I think
    you?ll get the same trouble. If not , tell me!

    Thanks for your support.

    Cheers.
  • edited July 2002
    You can send us the report. We can trace through the convert routines even
    though we can't actually run the report over data.


    Cheers,

    Jim Bennett
    Digital Metaphors Corp.

This discussion has been closed.