This is an FYI....
I had a report that would ONLY print the first page. It didn't matter what filter was selected or if no filter was selected - it always showed only one page in the preview and printed only the first page. If the filter was changed, then the first page changed but only the first page was printed.
This report had been used for years without any problems and I didn't make any changes to anything that would have been expected to affect it.
After deleting one object at a time from the report I finally found the offending object and then determined that the problem was caused by using an "undefined" global variable in a conditional object expression. It was "undefined" because it was originally (in a previous version) a global variable but that global variable doesn't exist anymore. I recently made a change that eliminated the need for that global variable but missed the fact that it was used in this particular conditional object definition. Once the reference to the no-longer-needed "global" variable was removed, the report starting printing all pages again.
So, if your report only prints one page but doesn't show any error messages, check for conditional (or other?) expressions that refer to a global variable that hasn't been defined.
I had a report that would ONLY print the first page. It didn't matter what filter was selected or if no filter was selected - it always showed only one page in the preview and printed only the first page. If the filter was changed, then the first page changed but only the first page was printed.
This report had been used for years without any problems and I didn't make any changes to anything that would have been expected to affect it.
After deleting one object at a time from the report I finally found the offending object and then determined that the problem was caused by using an "undefined" global variable in a conditional object expression. It was "undefined" because it was originally (in a previous version) a global variable but that global variable doesn't exist anymore. I recently made a change that eliminated the need for that global variable but missed the fact that it was used in this particular conditional object definition. Once the reference to the no-longer-needed "global" variable was removed, the report starting printing all pages again.
So, if your report only prints one page but doesn't show any error messages, check for conditional (or other?) expressions that refer to a global variable that hasn't been defined.