Skip to Content
author's profile photo Former Member
Former Member

Crystal reports viewer stripping paperorientation

We are using VB6 and we have recently switched to CR11.5 R2a SP6 in anticipation of going to Win7, currently we are still on Win XP pro.

We are now having an issue where the paperorientation appears to be ignored or stripped when sending a multiple report object to the crystal reports viewer.

In addition this appears to only be happening on the end user computers and not the development computer.

This is in essence what we do:

Dim MultiReport As CrystalActiveXReportViewerLib11_5Ctl.ReportSourceRouter

Set MultiReport = New CrystalActiveXReportViewerLib11_5Ctl.ReportSourceRouter

Dim AckReportLion As crptAckNewLion

Dim BuildReportLion As crptBuildReportLion

do any report processing like setting database connection properties, recordselectionformula and suppressing report controls.

AckReportLion.PaperOrientation = crLandscape

BuildReportLion.PaperOrientation = crPortrait

MultiReport.AddReport AckReportLion

MultiReport.AddReport BuildReportLion

frmCrptEEreports.CRViewer1.ReportSource = MultiReport

CRViewer1 is a CrystalActiveXReportViewer

at this point we can't intercept anything as the CRViewer has control.

When the print button on the CRViewer control is pressed the user is asked to select a printer.

At this point either all of the reports come out as portrait or crystal throws an error that caused the application to terminate.

Also, it appears that if all of the reports are of one orientation it seems to work regardless of whether they are landscape or portrait.

But, when you mix orientation, that's when the problems start.

Any help would be greatly appreciated.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Jul 25, 2012 at 02:48 PM

    In addition this appears to only be happening on the end user computers and not the development computer.

    Thus it is an environmental issue...

    Make sure you are using the same SP CR runtime. Use Modules to compare between the user and development systems. See if there are updated printer drivers for the user computers. See if installing the same printer driver as what is on the developer computer will help.

    Note that CR XI R2 has been out of support since June of 2011, so no more fixes, etc., etc.

    - Ludek

    Follow us on Twitter

    Got Enhancement ideas? Try the SAP Idea Place

    Share Your Knowledge in SCN Topic Spaces

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.