1. Richard Donagrandi
  2. PowerBuilder
  3. Wednesday, 22 March 2023 18:17 PM UTC

I have a subreport on a report with a user-set message field. If the user adds a really long message, the message looks fine on the screen. The message field and bands, reports, etc. are all set to auto-height, and adjust to the size of the message with no issue. However, when this report prints, the message gets cut off. Neither the subrepot or the bands in the report(s) are utilizing the autoheight... 

Wondering if there is anything I can do to tell the report to print properly.

We have other subreports on reports that autoheight just fine on screen and on print. But I have no idea why I can't print this report.

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 22 March 2023 20:12 PM UTC
  2. PowerBuilder
  3. # 1

Hi Richard;

   Can you tell us ...

  • MS-Windows version & build
  • PB version & build
  • Default printer being used
  • DWO's printer settings being used?
  • Do you instruct the DWO to use the default printer settings?
  • Other printer information, etc

Regards ... Chris

Comment
  1. Chris Pollach @Appeon
  2. Thursday, 23 March 2023 02:09 AM UTC
Hi Richard;

Thanks for that feedback. That's a great idea to manually force the DWO's to migrate to your PB version. That's a migration step that does not happen during a normal App migration by the IDE. It's been that way since the days of PowerSoft and I have no idea why that was not addressed. I've personally experienced many times offkilter DWO behaviour which was fixed by the procedure that you did. Now I always update every DWO's source like you did. However, I wrote a utility PB App that does this automatically by using the Library export() & LibraryImport() commands.

As for your AutoSize issue, it's hard to know why. We probably need to see a simple test case using those DWO's that recreates this issue. Then we could possibly locate the cause of this weird behaviour.

In the meantime though, have you tried printing this compound DW Report on different printers to maybe see if a print driver might be the culprit.

Also, how does this compound DWO render as a PDF (as an interest sake)?

Regards .... Chris
  1. Helpful
  1. Richard Donagrandi
  2. Thursday, 23 March 2023 15:30 PM UTC
Actually, scratch that; there was no improvement updating the release version of the dwo. ... It just won't autoheight a calculated field containing a retrieval argument on a subreport when printed.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Thursday, 23 March 2023 15:55 PM UTC
Did you try my other suggestions?
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.