When we print a crystal report using crystalReportViewer1.PrintReport(); the printers pause between pages and the client have to press a button in the printer to print the next page. If the client uses the report viewer print button it works fine.
It happens in these printers:
-HP CLJ 3600
-OKI C5450
I've seen that happen when the report is set up for a different paper size than the printer is expecting - ie: your report is setup for A4 and the printer contains 8 1/2 x 11.
In the end we make it work by calling the reportdocument print function instead of the reportviewer's reportDoc.PrintToPrinter(1, true, 1, 1000);
Dont know if Graham awnser is ok thought if someone confirms this i will mark as correct answer too...
Related
I would like to display only 4 pages on my Crystal report, however, I am getting an extra empty page. I cannot pin the reason to what sounds like a trivial issue.
My report has the following:
- No fields in the main report - This is not avoidable.
- One sub-report.
- In order to have the sub-report header repeat I followed this method described here. (I just do not understand what the formula means and whether this is the reason for the extra page but I am getting a header as I require).
I am suppressing the pages in both the report and sub-report as follows: in the suppress I am using
if pagenumber>4 then true;
I tried to put in all my sections
Not(onLastRecord)
I am simply lost. All I need to do is print 4 pages only regardless how long the report/sub-report is. I also need the sub-report to have a repeating header. Thanks.
Try to reduce the size:
-If possible supress group and report footers
-Right Click on each section you can and select "Fit Section"
-Change the color of some sections so you can see if any responsible for the extra page
-Maybe the paper is set to letter ? : Go Design - Page Setup, set A4 or you can also try no printer to see if something changes ( this last one will change the format of your fields so backup before)
If you have any footer sections that are not being used, try suppressing them. This will remove empty white space that is added at the end of the report. Another option is to adjust the size of your top and bottom margins, providing there are no design conflicts in doing so.
If you have any white space at the bottom of the sections that appear at the end of the report you could also reduce the height of that section to remove the white space.
In MS Word for Windows 10, if you wish to restart page numbering from "1" in the middle of a large document, doing so is currently a 7 step process. For example, let's say you have a document with 4 sections and on each section you wanted to restart the page numbering from "1".
I had two related questions:
Is there a way that, not involving adding any code to the source material, that a user can restart page numbering with 1 or 2 steps as opposed to 7?
If no, did anybody have a script that would allow the functionality described above?
Thanks
You can set the page numbers to restart by right-clicking on the page number, selecting Format Page Numbers... from the context menu and then, in the dialog now opening, entering the desired start value. Seems easy enough to me actually.
If you want to make it simpler you can add the below macro to your Normal.dotm file. You can then add a button to your Quick Access Toolbar that you bind to the macro and the command will be a single click away.
Note that page numbering always works per section, so your document will already have to contain the respective sections.
Sub RestartPageNumbers()
Dim startingNumber As Integer
startingNumber = InputBox("Start page number at: ", "Restart Page Numbers", 1)
ActiveWindow.View.SeekView = WdSeekView.wdSeekCurrentPageFooter
With Selection.HeaderFooter.PageNumbers
.RestartNumberingAtSection = True
.startingNumber = startingNumber
End With
ActiveWindow.View.SeekView = WdSeekView.wdSeekMainDocument
End Sub
I have a button on a form that I want the user to be able to print a report without opening the report or viewing a print preview. This is my code so far:
DoCmd.OpenReport "DisplayUncompleteProjects", acNormal
DoCmd.RunCommand acCmdPrint
But my problem is that it is print both my form and the report. I just want to print the report. But I also don't want the user to leave the form page. (aka when they are done printing the report all they can see is still the form.)
Thanks.
Leave out the second line, which just prints the current object, and run only:
DoCmd.OpenReport "DisplayUncompleteProjects", acNormal
Hi I want a page break that goes after each group except for the last group. Currently my page breaks separates all the groups nicely, but I would like the last group to be connected to the last page. The page break separates my last page footer, leaving a huge amount of space on the last page. Is there any way to do this?
I'm thinking of hiding the last page break but I'm unsure of how to do it.
Attempts to do a put into $P{REPORT_PARAMATERS_MAP} within the print when expression band of the summary band have been unsuccessful.
I tried placing the following into the 'print when expression' band of the summary band:
new Boolean($P{REPORT_PARAMETERS_MAP}.put("LastPageNumber",new Integer($V{PAGE_NUMBER}.intValue()-1)).equals("dummyPrintWhen"))
And using this on 'print when expression' of the break:
new Boolean(!$V{PAGE_NUMBER}.equals($P{REPORT_PARAMETERS_MAP}.get("LastPageNumber")))
But it's not working the way I want. It still gives me the last page footer all by itself on another page while still leaving a large amount of space on the previous page.
By taking out "!" on the break's 'print when expression', the breaks don't happen and I get my last page footer on a page all by itself as there is no more space on the previous page.
----------------------------EDIT--------------------------------
Printing $P{REPORT_PARAMETERS_MAP}.get("LastPageNumber") for every page
gives me null.
----------------------------EDIT--------------------------------
What am I doing wrong?
I'm currently using iReport 3.0.0
What if you use ?
new Boolean(new Boolean($V{PAGE_NUMBER}.equals($P{REPORT_PARAMETERS_MAP}.get("LastPageNumber")))==false)
I think what I'm trying to do might not be possible simply because the last page number can only be compiled at the end of the report, while the page breaks happen as the report is compiled.
I think this can be confirmed by nobody answering the question on this page: http://www.coderanch.com/t/579950/open-source/Jasper-report-store-total-number
I have a Crystal Report 11 file that is a letter. The first Details section contains a large text box that has print date, address block, and the salutation line. Every once in a while, the last line of the text box gets cut off so that the salutation isn't seen. It's very inconsistent in that sometimes, I run the report for one person in my system and the text is cut off, but if I run the report a few hours later for the same person, without having changed the values of the address or name in my database, then the letter looks fine.
I increased the text box height and the Details section height, but the problem still occurs intermittently. Has this happened to anyone else, or does anyone have an idea what could be causing this?
Normally this should be working if you check the "Can Grow" option in the common tab of the "Format Field/Text" settings. With that option checked it shouldn't matter which height you set.
This is difficult problem that you have to attack from 3 different fronts:
Software Hot Fix
Default Printer
Form Authoring
Software Hot Fix: You'll need to download the CRRuntime that includes Hot Fix 20. This Hot Fix addresses truncation problems when making a PDF. You can find it at http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_64bit_13_0_20.msi
Default Printer: The printer you use when authoring a report must match a printer when you are rendering a report. On our servers, there are no printers installed except the Microsoft XPS Document Writer. Be sure to select that as your default printer when writing the report.
Form Authoring: When you add a database field to your report, don't drag it from the field explorer onto the design surface. First insert a text object onto the design surface. When you've positioned and sized it, then drag the database field onto the Text Object. For whatever reason, the database field will wrap better when it is enclosed by a text object.