Okidata 320 turbo

[Former Member]

We are using two different programs that use Crystal Reports 10 to handle their report printing. In one program we use a work ticket on an OKI 320 trubo printer.

I have spoken to OKI and have set all the defaults to the custom size. For some reason the printer changes size every time we attempt to print. Both of the software companies have told me that the problem is that Crystal no longer supports OKI printers. If this is so then what do we do? What's the workaround for a legacy problem?

If not any suggestions??

[former_member11696]

We can't fix their programs. Please log the issue with them

[Former Member]

We are using two different programs that use Crystal Reports 10 to handle their report printing. In one program we use a work ticket on an OKI 320 trubo printer.

I have spoken to OKI and have set all the defaults to the custom size. For some reason the printer changes size every time we attempt to print. Both of the software companies have told me that the problem is that Crystal no longer supports OKI printers. If this is so then what do we do? What's the workaround for a legacy problem?

If not any suggestions??

Hi Bruce

Please provide the following details:

1. Two different programs- what do you mean by this statement

2. Do you have Crystal Reports embedded in any other software

3. Are you facing the same problem when you try to print the reports from a crystal reports 10 stand-alone application.

4.Is the problem specific to some report(s) or it happens with every report.

[Former Member]

Our two programs are Cyma (an accounting program that also uses Pervasive) and Temps+ (a program for the staffing industry) Both of them use Crystal as their report program.

When we print directly from the server everything works fine it's only when we try to print from the workstations that we have the problem.

[Former Member]

Something to check, may or may not be related

- you mentioned printing from workstations, we have found that how the printer is actually connected to the workstation makes a huge difference in how crystal sends a job.

= if the workstation is connected via a share from the server versus setting up a port on the workstation that connects to the printer and then adding a printer to the workstation using that port

when printing a report from cyrstal to the printer, it should show as different sized jobs and the names of the job should also be very different.

[Former Member]

Joe Moore stated: Something to check, may or may not be related

- you mentioned printing from workstations, we have found that how the printer is actually connected to the workstation makes a huge difference in how crystal sends a job.

= if the workstation is connected via a share from the server versus setting up a port on the workstation that connects to the printer and then adding a printer to the workstation using that port

when printing a report from cyrstal to the printer, it should show as different sized jobs and the names of the job should also be very different.

---

What is the huge difference you are talking about? Is it performance related or what exactly.

[Former Member]

( we use active X custom interface to crystal runtime )

A report that is sent to a dot matrix printer that is shared

= Document data type NT EMF 1.008, size 17,580 bytes,

= Document name , Crystal Reports Activex Designer - SO - Invoice Entry Audit List

= this does not print very well.

same document printed to same printer via printing to a port setup on the workstation that goes to the same printer

= Document data type RAW, size 10674 bytes,

= Document name, Remote Downlevel Document

= this prints fine

Edited by: Joe Moore on Nov 24, 2008 8:30 PM