Crystal Reports / ZetaFax print question 1

[GhostWolf]

I've created some POs that print perfectly from Crystal to an HP printer.

However, when I send the same document to a ZetaFax printer several of the text boxes get ugly.

I've tried changing fonts, font sizes, spacing, field sizes, and print resolution - all to no avail.

Anybody with any ideas?

 

[synapsevampire]

Check for an updated print driver.

Crystal is printer dependent, and if you're using fonts not supported by the printer, you'll also have problems.

When you change to the Zeta print driver and preview, does it look bad? If not, I'd contact the vendor and explain your problem.

An alternative might be to export to a PDF, and then print to the Zeta driver from the PDF.

-k

 

[GhostWolf]

SynapseVampire,

You hit on exactly what I found: "Crystal is printer dependent" - but I found it by accident!

Once I defined the POs for the ZetaFax printer, everything went beautifully.

Sadly, that means we have to have one form defined for laserjet printing, and another for the fax printer - so now I've got a mess of forms to copy and modify...

Thanks for the tip.

 

[GhostWolf]

But now, in the brutal light of another morning: this just doesn't make sense!

I've got another CR report, being generated by a VB app, that prints perfectly whether it's being sent to a laserjet or ZetaFax.

Not to sound like the typical 4-year-old, but "why" would the report work correctly from a home-grown app but not from a "foreign", (read canned), app?!

 

[synapsevampire]

Noty sure what canned app means, but I'd suspect that they have a bad design or driver.

-k

 

[GhostWolf]

Some day I'm gonna learn the correct term for off-the-shelf software - you know, the stuff you can buy somewhere for a lot more'n it's worth, (like Billy Gates' products) - and quit coming up with words like "foreign" and "canned" for it.

 

[Lochbel]

We found a problem printing to Zetafax 8 after upgrading from CR8.5 TO CR9.0.
Zetafax failed to recognise the fax number embedded on each page.


Suspect it is text driver problem within CR9.0, but would welcome any feedback. Reports in CR8.5 working ok.