on 04-14-2009 11:40 AM
I am using VS 2008 with the embedded CR (CR basic for .NET).
I have a report which is designed for A4 paper size and when printed, previewed and exported to PDF format it is created in A4 paper size, but not when exporting to word where it is in letter paper size.
Any ideas why and what can I do to fix this?
I am using VS 2008 with the embedded CR (CR basic for .NET).
I have a report which is designed for A4 paper size and when printed, previewed and exported to PDF format it is created in A4 paper size, but not when exporting to word where it is in letter paper size.
Any ideas why and what can I do to fix this?
Note: I use Word 2007. When in preview and I select "paper size" icon the letter paper size is shown as selected. However if I choose the print output format (not sure about the exact name of this dialog in english since I have a localized word version) then papersize is shown as "user defined" and with width/height with legal paper size.
Sorry aout the double post. Editing the original message went wrong.
Edited by: Magnus Bergh on Apr 14, 2009 12:49 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First, download SP 1 for CR 10.5 from here:
https://smpdl.sap-ag.de/~sapidp/012002523100009351512008E/crbasic2008sp1.exe
Let me know if that does not help. This may be a bug and I'll need to report it to QA / R&D for a fix.
Ludek
I have not yet tried the SP but I found another solution that seems to solve the problem. The report is designed for A4 but when exporting to word it does not seem to reespect that (does for PDF though). However if I set papersize in code (report.PrintOptions.PaperSize = PaperSize.PaperA4) prior to exporting then it works fine.
Was the CR Basic SP1 included in the VS 2008 SP1 or do I still need to install it? The CR Basic SP1 does not seem to include any fixes that might have to do with my problem or any other problems I have had. Is there more fixes done which is not present in the read me file?
+Was the CR Basic SP1 included in the VS 2008 SP1 or do I still need to install it? +
- no it was not. I suppose once .NET is release with the CR bundle, that is it as far as MS + CR. So you do have to apply the SP for CR separately.
The CR Basic SP1 does not seem to include any fixes that might have to do with my problem or any other problems I have had. Is there more fixes done which is not present in the read me file?
- no other info. I suppose my thinking is that applying the SP should be the 1st thing to do anyhow. I have seen SPs with fixes that were not actually documented. However, if you are OK with the work-around you discovered, it may be just as well to go with that (why fix what ain't broke...)
I still plan on testing this when I get a bit of time
Ludek
Edited by: Ludek Uher on Apr 16, 2009 7:17 AM
ok, thank you!
I agree that applying a service pack is usually a good thing to do. However, doing so would require us to do an upgrade of runtime at the client's site (200+ workstations even though upgrades are pushed out using SMS) which is a bit of work and involves a third party doing it, so I prefer not having to do it if not necessary.
Are you exporting using code, or the button on the viewer?
Have you tried the code solution:
report.PrintOptions.PaperSize = PaperSize.PaperA4
What is the version of the CR assembly crystaldecisions.crystalreports.engine.dll referenced in your project?
Also, see if enabling the "No printer" option on ther report helps.
Ludek
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.