• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3261
  • Last Modified:

Crystal .NET viewer printing - paper size/orientation issues

We are currently working with Crystal XI and distributing reports through a 3rd party distribution tool that utilizes the Crystal Active X viewers.  We are in the process of migrating to Crystal 2011 which uses .NET viewers (not active x).  In our reports I have the "No Printer" option checked in the report's design.  In Crystal Active X viewer, when a report is run and you click the print button in the viewer, you can see in the attached on slide 1 that it is picking up the Page set up in the report's design and passing to printer.  Legal/landscape/Actual size.  When I run this same report through the .NET viewers it defaults to Letter/Portrait and for extra fun, Fit to Page.  Ideally we'd like the .NET viewer to do the same as active X and know by the report's design what the paper size/orientation needs to be.

In slide 2, it would ideally have Actual size marked as default, auto portrait/landscape is fine (but I had to select it the first time and then it stuck), and then it already have the correct paper size (legal) selected when you click Advanced to see those options.

The default printer in the report is on the server running the app, so that is not the cause.  All variables are in place on our new Crystal 2011 environment that are on our current Crystal XI.

Please tell me this is fixable!  I have looked for solutions to this every where, including a similar post here, and have yet to see a solution.  If we have to tell users that they now need to select their paper size and check off Actual this will be seen as extra step and not an improvement incentive to move to a new platform.
CrystalNETprinting.ppt
0
melandcurt
Asked:
melandcurt
  • 7
  • 4
2 Solutions
 
mlmccCommented:
CR 2011 does NOT include an SDK and is NOT intended for use in applications.

You should be using the version that is available for Visual Studio.  If not included with your VS, it is a free download.

What version of VS are you using?

The .Net viewer is different from the AciveX viewer and may not support the features you are trying to use.

mlmcc
0
 
melandcurtAuthor Commented:
We are not using VS. We design the reports in the Crystal Reports 2011 designer and then publish them in a 3rd party report distribution tool that uses the crystal . NET runtime viewers.
0
 
mlmccCommented:
You probably need to discuss this with the vendor of your 3rd-party tool.

Which 3rd-party tool?
Does it support CR 2011?
Perhaps you need an upgrade from them.

mlmcc
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
melandcurtAuthor Commented:
It is not the 3rd Party tool.  Yes, they support .NET and crystal 2011.  We are on their latest version.  They only use the crystal viewers for report display and printing, nothing more.  If you look at my attached screen shots it is the functionality within the crystal viewer that has changed. From everything I have read it is more than likely the .NET viewers for this version of crystal.  I have read that they tend to take on the properties of the printer defaults as opposed to the report design page setups like the Active X viewers do.  I have done a lot of "homework" on this matter and was hoping someone here has found something to work around this or a solid solution, but it does not appear to be the case.  I don't feel like I'm getting much further here b/c I think this is just how it works. Which would be a major set back for Crystal b/c currently the users click a printer button inthe viewer and it knows what paper size and orientation to print and now they will have to select these things. Also the default to Fit to Page instead of Actual size is a big inconvenience.
0
 
mlmccCommented:
Crystal does save the printer information but it is saved for the printer the report was built with.  If that printer is not available then the default printer is used and the defaults for that printer are used.

I believe if you install the printer driver the users have on the development machine then you can open the report, change the printer, and save the report.  It should run as you desire.

mlmcc
0
 
melandcurtAuthor Commented:
We have users in many different states that would not be printing to the printer the report is designed with.  All of the print drivers and printers that are on the server with the Crystal XI version are on the Crystal 2011 version.  The reports have the No Printer option selected in both versions but has the paper size and orientation set.  The active X viewer accepts this and no matter what printer is selected it knows the report's design.  .NET printers do not seem to care about this.  Currently I am the only one using this version as we have not deployed it yet.  The default printer on my machine is on the server running the Crystal 2011 and this does not change the outcome even when I save that printer in the report's design.  
The other recommendations I have seen is to change the default printer settings to be the paper size and orientation (in this case legal) you wish is to be and then it will work, but I have my doubts about this as well b/c like I said we have users in different offices and states that will print to their default printers, not the one the report is designed with.  I will be trying this today however to see if it works.
0
 
mlmccCommented:
CR2008 changed the printer interface.  I think CR2011 has the same options.

There is a new option to DISSOCIATE FORMATTING PAGE SIZE AND PRINTER PAPER SIZE.

Try clicking that then setting the paper size.

The NO PRINTER option was used to optimize the report for screen display.

mlmcc
0
 
melandcurtAuthor Commented:
Have already tried various combinations of this as well.  Having a printer and checking the Dissociate option.  Having No printer and Dissociate.  Same outcome.  I am having my IT guy verify that the print drivers on this server are in fact the same as our current production server, but I believe they already are.
0
 
melandcurtAuthor Commented:
I believe we have the solution to this after logging a call with SAP directly.  The .NET Crystal viewers by default come out of the box with a print mode property of pdf.  This option is what is giving the undesired results.  The solution is to change this print mode property to ActiveX which will then use the Active X print options.  I will attach screen shots of the solution.
0
 
melandcurtAuthor Commented:
So my last comment was accurate and our software vendor for our 3rd party reporting tool has a Print mode option which makes the Active X print control work. After switching this on we were getting "a Communication error has occurred.  Printing will be stopped".  Then I stumbled across a report that the print control worked.  Baffled, I did more digging and came up with a lady that had an issue where her report parameters were buggy and sending extra values to the query which threw an error.  Ding ding! The report that worked has NO parameters to fill in. So I tested a few more reports without parameters and all the the Print Controls worked.  So the software vendor is now looking into if there are extra parameters being thrown in code in the background.  Will keep posted.
0
 
melandcurtAuthor Commented:
The suggestions given by the expert were all that I had come across with research online prior to me opening the call here.  Also they stopped responding after their 4th comment.  I logged a call with SAP and got the correct answer.  Also worked with out 3rd party vendor as some of the capability was within the product, but there were a few bugs.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 7
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now