Access 2010 reports

Have a look on following links to set it up with 2003 Compatibility in 2010

http://www.addictivetips.com/microsoft-office/access-2010-convert-pictures-to-bmp-access-2003-compatibility/



http://allenbrowne.com/access2007.html

There are no pictures in any of the reports but i did tick the check for truncated field, but there was no change.

Did not see anything specifical helpful in the allenbrowne site other the the standard stuff.

You say that ALL of the reports do this?

Are you certain there is a valid Default Printer setup on the machine? By "valid" I mean an acutal, physical printer that you use, and not a virtual printer (like a PDF printer, for example).

Are you certain that your printer is properly installed on the machine, and that you have selected the correct Printer for your report? This is done in the Page Setup area of the report. Most people leave the setting to "Default", but you may have a specific printer you'd like to use.

Yes there is a valid printer setup on this machine a Brother MFC-8840D, the same printer that prints correctly under Access 2003 but not from Access 2010.

If you preview the reports, do you also see the extra page? Or is this only something that occurs when actually printing to hardcopy?

Do you have another printer you can test? That is, set the machines Default Printer to a different printer, and see if Access formats the page correctly?

There are several formatting options that can Force a New Page, but this behaviour would be seen on earlier versions as well. Still, it might be worth your time to review the settings on one or two fo the reports to insure all is well.

Yes you get the extra page on print preview as well. I have three different printers which when set as default also display and give the extra page.

Force a new page is not on and as you said would have been seen on earlier version. I thought it might be something to do with having sub-reports in the main report, but I have deleted them out and it make no difference.

Have you tried this on more than one machine, with the same results? I'd be curious to see if this "follows the database" or is specific to that machine.

It follows the database. I have tried it on stand alone machines as well as the original server and all the same.

Have you tried a Compact/Repair on the database? This can cure quite a few ills. YOu might also try a Decompile. To do that:

Build a shortcut with this as the Target:

"full path to msaccess.exe" "full path to your database" /decompile

After doing this, open the VBA Editor, click Debug - Compile. Fix any errors, and continue doing this until the menuitem is disabled.

Now compact again.

Might also be a good idea to import everything into a new, blank database.

Hmmm ... I assumed you actually had something in the Header and/or Footer. I've noticed this same behavior in earlier versions as well (i.e. the printing of a blank page if i leave a blank Header/Footer in, depending on the various formatting options I choose for those sections).

Obviously, if you don't need either of those, then you certainly don't want to include them.

I can't see why should a blank footer force a new page, unless code is added to force a new page.

No the Report header and footer were both empty. The Page header and footer have fields in them, and the report behaves as it should.

There was no code behind any of the report H and F.

It may be that one of your margins is "on the very edge" of what Access considers the end of the page.

Try making the margins a little bigger.
Try making each section a little shorter.

Issue like this can be difficult (at least for me) to troubleshoot without a sample DB
So if none of our other suggestions help...

Sample database notes:
1. Back up your database(s).
2. Combine the front and back ends into one database file.
3. Remove any startup options, unless they are relevant to the issue.
4. Remove any records unless they are relevant to the issue.
5. Delete any objects that do not relate directly to the issue.
6. Remove any references to any "linked" files (files outside of the database, Images, OLE Files, ...etc)
7. Remove any references to any third party Active-x Controls (unless they are relevant to the issue)
8. Remove, obfuscate, encrypt, or otherwise disguise, any sensitive data.
9. Compile the code. (From the VBA code window, click: Debug-->Compile)
10. Run the compact/Repair utility.
11. Remove any Passwords and/or security.
12. Post explicit steps to replicate the issue.
13. Test the database before posting.

In other words, ...post a database that we can easily open and immediately see and/or troubleshoot the issue, and if applicable, also include a Graphical representation of the Exact results you are expecting based on the sample data.

JeffCoachman

I am accepting my own solution as it solved the original problem I had.