Report PrintPreview is fine, but prints blank page

gold007eye

Registered User.
Local time
Today, 11:41
Joined
May 11, 2005
Messages
260
What I have is a form where you put data in "Report Type", "From Date", & "To Date" and click submit. This in turn runs an append query depending on the report type selected and opens the report in the Print Preview mode. Now the problem I am having is that the data is showing up correctly on the Print Preview, but when you go to print the report it is printing 1 blank page with a little grey box in the upper lefthand corner.

Has anyone come across this before or know what would cause it? I have another database that does it sparatically. With this one it does this every time and I can't figure it out :confused:
 
1) Have you any page breaks in your report

2) check the page setup & make sure you report is not too long.

Hope this helps
 
No Page Breaks.

I used the Report Wizard to create it. It is a one page report. :\
 
Report Width

This usually happens when your page setup has (let's say) a left and right margin of .5 in and your actual report width is something like 7.6 in. So the max width your report can be is 7.5 in...since the report is 7.6in you get a blank page.
 
Page width is only 6.5" with a 1" margin all around so it should be within the confines of the page limits.
 
Had this myself once.

If you are dumping to a network based printer particularly sometimes the kind network people set ity up so that you get a blank page between jobs sent to the printer.

They do this so that it is easy to separate different reports from different users.

Worth checking

L
 
Thanks for the help :) It is a network printer, but I that wasn't the issue. I figured out what was causing the problem. I had created a custom toolbar for "printing" and I created an autokey macro ^P to give the user the option of the number of pages, etc. to print, but it seems that is what was causing the blank pages so I just copied the "print" button from the file menu and put it on the custom toolbar and everything has been fine since.

I am glad I figured it out cause one of my other databases was doing the same exact thing (except it was sparatic) and I couldn't figure it out so hopefully this has fixed the issue for both databases now :) Thanks again everyone for your input and I hope this will maybe help someone in the future.
 

Users who are viewing this thread

Back
Top Bottom