
Originally Posted by
NTC
it is frustrating when an app behaves differently in a new version. I don't think it is that the database is not compatible with Access 2010 generically. It is just an issue that needs to be solved.
one point of complication involving Reports is that that their behavior is dependent upon the graphics card of the PC - meaning that it is possible the behavor would be the same if you installed Access 2003 on this same PC; but for now - I would just hold that issue to the side.
Reports have the group parameter which will dictate page break location. There is also a page break control which does too. White/blank space can alter the page break as will the Can Grow property. Fundamentally I would begin by inspecting the report when on the 2010 machine in its design view. One of these aspects may be in play in the 2010 app that isn't, for some reason, in 2003. Why? I can't say. Sometimes we find things that just need to be tweaked.
(Because of the graphics card issue one should definitely not expect 2 machines to have exactly the same row count when there is an auto page break even when 2010 is not involved.) Also - if you are stumped; You might consider whipping up a new report in 2010 - at least just the bare features of it - using the same record source - - just as a sanity check and for comparisons.