Hi Ludwin
If I have understood correctly the problem is that although you have a page break after the employee, when you duplex this you need to adjust for odd and even page counts and so throw 2 pages when the previous employees was only an odd number of pages.
I've not personally done this but here are my thoughts / options:
You could work out based on the number of rows reported for each employee (computed column count(dataitem) for employee) the number of pages that would have been printed.
Using this you can:
1. Insert a page break control on the group footer if the number of pages is odd ASCII Code 12 would do it.
2. Force dummy rows into a nested DW in the group footer that will force it over a page. Perhaps the nested DW could recieve the number of rows for the employee and based on this select dummy blank rows from a sql query to make it enough to force the page.
All a bit dirty I know but may well achieve the result you need. The only other thing your would need to consider is if they are not printing duplex it would have blank pages in the report also the page length may vary on different printers becuase of the margins....
The easier way to do this in PB is to report each employee separately as a separate print job. The printer will feed automaticaly after each job.
Hope that my old grey wisdom of these srots of problems can help you now.
Cheers
David P
