Goodmorning,

Recently it came to our attention that there are printing errors cropping up during our A/P cheque runs. Every once in a while, the bank routing information (MICR) coding will get "botched" Overprints of the second code grouping make the codes illegible, or there is a X-Y shift and then a re-print of the second code grouping. We've even swapped printers in the meantime, and it is still occuring.

It appears quite random.

We've had some issues with printing picking/packing lists from O/E. In some cases bill to/ship to information is missing entirely until we restart O/E and reprint. This occurs regardless of system or printer, at random times.

Any ideas?

Thank you.

Have you made sure that you are running the most up to date printer drivers for your printer and operating system?

Is it re-creatable in the sample data?

Yeah, the printer is brand spanking new, with the latest drivers from Xerox. A Workcenter 7328, latest postscript driver.

As far as being re-creatable, it is really random. When going through our stubs from the bank, it would only appear 1 in 50. (at best guess, as we haven't scoured the entire collection.)

We will create some bogus data and see what appears when we do a fake A/P run.

Are you using the latest drivers off their web site, or the drivers on the CD in the box? Are you using the postscript or PCL driver? Can you try whichever one you are not using?

"Random" errors are always a pain to track down. Since this hasn't been reported as a problem at other sites, I'm more inclined to point a finger at the printer and/or its driver.

Latest PS drivers from the website, but I will switch over to PCL, just to give it a try. The previous printer used PCL drivers installed, with virtually the same controller, same issue. They were both Xerox printers.

Crystal is used as the backend for Adagio report generation. I have found a few references to certain versions of Crystal and Xerox misbehaving.

Any other thoughts?

Crystal is not used to generate check forms in Adagio. Adagio uses a propriety reporting engine for that function (and for all other forms that are specification driven).

When you use PCL, try using PCL 5 not PCL 6 if given the choice.

Another suggestion, before printing your checks, preview them and see if the problem occurs in the preview (if not, then close the preview screen and print normally). If the problem occurs, then it is likely to be a printer driver issue (and you have caught it in time); if the problem doesn't occur it is likely to be hardware related.

Steve

Thanks Steve.

We've swapped drivers ... just waiting for some print jobs to come through.

We've had it happen once in a while with specifications in O/E. Under preview, everything looks fine. After we print, we are often missing data, as stated in the OP.

One work around was to run it through acrobat and generate a PDF. We can then print the PDF on any printer without issue.

There was once a British stand-up comic who quipped to an American audience: "Well, blokes, we invented the language and what you have done with it since then cannot be blamed on us!"

Well, PCL is a little like that. HP invented the Page Control Language and has made several expansions to it, but other printer makers may or may not implement it exactly as HP designed it, hence the intermittent problems.

Sometimes, but not always, you can resolve the issue by installing the native Windows driver for a very common PCL printer, like HP LaserJet 4, and pointing it at the printer you are using. If this works, then select that printer for Adagio and the native driver for other programs.

Tried switching to PCL drivers. Same issues. I re-installed the PS drivers and set the driver to send the fonts as soft-fonts (skip printer substituion), and the problem with the MICR overprinting was gone.

Must be been how the printer was interpreting the MICR font.

Thanks for your help.

Thank you for taking the time to post the solution here so others searching this forum for similar issues can benefit from your detective work.