Hi Susan,

These errors may have been in the data for sometime, but the DIC was not check for this type of error (orphan records) before the update. DataCare may not have been updated for this error yet as it is a minor error and will not cause any reporting problem and is not related to the statement printing issue.

When you print your statements are you using any of the range(s) to control which statements are printing?
What is the sort order of the ranges you are using?

Hi Chris,

We normally sort by date order, but I tried document order as well and the result was the same.

I'm not sure if this has anything to do with it, but I just remembered one more thing that I did in August. In User Preferences on the Report Tab, I changed the Date format (Detail) to MM/dd/yyyy.

I just tested 3 times and had successful results by choosing "use selected specification" instead of "use customer specification", even though they both result in using the same spec. Our customers are not set up with a statement spec and I checked and confirmed they are all blank. The spec is specified by default in the company profile.

The font on the statements is different than it used to be, but "use selected specification" is definately working consistently.

Hi Susan,

While the output might be the same in your case, the forms printing process is completely different when you choose to use the customer statements. In that case, for each customer, the form name is inspected and the form loaded if it exists. If it doesn't exist, then the one in the company profile is used. The printer is then opened to find out what it is capable of (paper size, colour etc). The form is converted into a series of printer commands, the printer is closed and the memory used by the form is discarded. This process is repreated for each customer.

When you use a specific form for the entire run, Adagio Receivables can load that form, open the printer once, send all the statements to the printer in one job, and then close the printer and discard the computer memory it was using.

If either Receivables or the printer driver does not properly free the memory it was using to print the form, eventually your computer will run out of memory to use or reference some memory improperly. This will likely generate the error you saw.

We'll take a quick look to see if it is a Receivables problem. The fact that AdagioPDF worked properly, but the printer did not would tend to point away from Receivables having a problem.

It's weird that Adagio.pdf works because not only does it not work when printing to our main printer, it also does not work when printing to PDF Creator and not even when printing to Screen. Adagio.PDF is the only way I can print using customer specification. When I change it to "use selected specification", I can print to Screen, Printer, PDF Creator and Adobe PDF with no issues.

Thankfully, I don't need to use customer specification since "use selected specification" does what we need it to. The only time this would become an issue is if I needed to use different specs for different customers.