Corrupted output with PrintToText

rbuser

We have a report that generates a RBuilder archive first, then uses
PrintToText to generate a fixed-length text output of the same report.

We have hundreds of customers that have used this report multiple times
a month for several years.

Last month, we had one customer that had a problem with the generated
text file. Two lines of the text file were "merged" into a single
line. It wasn't just that a gap of text was missing. The resulting
line had a segment of the first line, followed by a segement of the
second line, followed by a different segment of the first line,
followed by a different segment of the second line, etc. It was very
strange.

Has anyone seen anything like this? I can only chalk it up to an I/O
problem on the customer's server. However, Windows' Event Log is not
reporting any I/O errors on the disk.

Thanks

nicocizik

Hi Jon,

We have not seen this issue before.

Which version of ReportBuilder and Delphi are you using? Does this issue
only occur for a specific report? Has this report ever worked in the past?
What about the report with issues is different from other reports that
export correctly?

--
Regards,

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

rbuser

Nico Cizik (Digital Metaphors) wrote:

You basically answered my question, in that the issue has not been seen
before. At this point, I'm chalking it up to a fluke and we'll wait to
see if it happens again. But I'll answer your questions, since you
asked them.


Delphi 6 and RB7. Not that it matters, but the report was originally
created with Delphi 4 and RB5. (We're in the process of migrating
to RB11, see PS below.)


This is the first time we've seen it, so we've never seen it occur on
another report.


Yes, consistently.


This is one of our most complicated reports. For example, it is the
only report where we use TppPageStyle. We also change the visibility
of many elements of the report based on whether we're generating to
archive or text, due to the visual appearance of the archive version vs
the text version. But these changes are made before calling
PrintToFile, rather than making the changes dynamically while the
report is running.

Jon

PS: We're in the process of migrating our product to Delphi 2009 and
RBuilder 11, but we're still in the early stages. Note, so far, so
good. The core applications are building with Delphi 2009 & RBuilder
11, yet they load previously compiled reports that are in a DLL built
with Delphi 6 & RBuilder 7. Those reports execute perfectly, and we're
able to view the generated archive file in the core app. I'm very
pleased! Towards the end of the migration, all of the reports will be
rebuilt in D2009/RB11.)

nicocizik

Hi Jon,

Thanks, let me know if this ever becomes a problem again (especially with
the latest version of ReportBuilder) and we can try to track it down.

--
Regards,

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