Hopefully the work going into the JC module to prepare the upcoming service pack will help them figure it out, it's one of the few remaining current releases that still can print to the problematic printer brands.

Hello Sam,

Softrak programmers have spent a great deal of time investigation this issue. The error is happening outside of Adagio; at one point, it was traced to a problem deep in Crystal.

None of the programmers who have worked on it so far have been able to produce a fix.

Support: I'm sorry, the problem is not deep within Crystal.

If the report is Previewed using a different printer driver, then it can be printed from the Preview screen to a Sharp/Kyocera printer. That's printing from Crystal Reports directly to the printers.

Furthermore, if you Google for "Crystal Reports Sharp printers", the only results are a small handful of matches over the past 15 years and none of them correspond to what we are seeing. If this is an inherent problem in Crystal Reports, wouldn't there be more hits? And if there were, don't you think that SAP would have solved any problem working with major printer manufacturers like Sharp and Kyocera?

This is reminiscent of the Windows 10/11 situation 12 months ago where Support said (repeatedly) that it was a Microsoft problem. Then one day in January Bob Wisener took a look at the issue and 30 minutes and a cup of coffee later, he had diagnosed the problem and found a solution.

Do any of the developers at Softrak even have a Sharp or Kyocera printer? Since Sharp printers are usually multifunction copiers/printers costing thousands of dollars, I'll go out on a limb and say "No".

Update:
Terry has assured me (via email) that a lot of testing has been done without success. Those doing the testing have been people I trust and respect (Cornelia, Chris). Now that I know who wrote the post this morning and who has been doing the testing, I realize that I oversimplified the situation. I trust that the best people are on the case and they can find the solution if they are given the required resources.

Hello Bruce,

We were able to duplicate the error. We were never able to consistently trace the source of it.

None of the programmers who have worked on it so far have been able to produce a fix.

The reason I was hopeful is that I expect the next JC release will have the problem, it's probably going to become broken over the course of the work being done now. Hopefully someone is able to learn more while it is happening.

If my hypothesis is wrong, and it becomes the first 9.3+ release without this problem, that will also be very interesting.