I've seen that case before but the issue is data related and not because a PU "broke" it. Do you have any 3rd party program that intergrates with AR? You can go back to PU3 and confirm if the issue is indeed related to PU4. There's no database change between PU3 and PU4/PU5 so it's safe to roll back. If you see the 100 statements in PU3, open a case with Sage 300 support and send us the data for review.

Thanks .. I will give that a try and let you know if it resolves the issue.

An update on this issue.  I upgraded this client to ERP 300 2014 last week and the issue still exists.  There are no third party products and the product is now installed on a brand new server and the only thing on that server at the moment is the Sage products.  Since we did a fresh install and only the 2014 product, the Crystal Report is obviously a fresh, standard one so that out rules any issues that may have been caused by a modified report.

Install is Sage 300 ERP 2014 Premium on Server 2008R2, all patched.  

I have double checked that the Print Statements option is turned on.  30 statements should be printing and there are only 4 printing.  Another strange thing is that when we select Reprint and put a date range in, it will include even paid invoices on the statements.  All customers are open item customers.

This just started happening after Product Update 3 was applied to their ERP 2012 in December.

Any suggestions?

Thank you for the update. Sage 300 ERP 2012 PU5 has fixed many of the emailing issues. Did you try it? If PU5 doesn't fix it, open a case via chat. Tell them to pass your case to me and I will get someone from R&D to remote connect to your client. As for the re-print with date range, try it first with sample data to confirm if we are looking at a possible data issue or a program issue.

Just to clarify, they are no longer on 2012. I upgraded them to 2014 last week.  It is a fresh install of all programs on a new 2008R2 server, the only thing carried over from the old install was the data.  The data integrity runs as clean.  They have 5 databases and I believe this situation is occurring with all of them, but I am just going to remote in and test the other 4 and then will connect via chat.  Thanks.

I see. So I assume they have 2014 PU2 (with the hot fix). So if they already have PU2 mention that when you open the case and we will schedule someone from R&D to take a look. Any chance if the client is using Terminal Server?

FYI, data integrity check only checks some scenarios. Otherwise it will take forever for DIC to finish if all scenarios are included in the programs.