Sage 100

Somewhat of a routine upgrade to v2015 Std from v44. Most issues are resolved with the exception of printing bar codes a SO form via dot matrix OKI printer. Former setup was via a TS 2008 R2 connection using a TS print Queue. New set up is a 2012 TS connection using the identical TS print Queue via the same OKI printer set up. No changes were made to the Crystal form with the exception of the Crystal update. Everything on the form is readable except the bar code (which doesn't even look like a bar code now. Form prints when outputting to a laser jet Azalea fonts were installed on the server. Thoughts

Does the font show correctly when previewed under Windows \ Fonts?

I had issues with bar code fonts after a recent upgrade. I had azeala installed, and tried all of the bar code fonts yet still had issues. Finally I right clicked on the field and chose ""Change to Barcode"". That worked for me.

Interesting @DougHiggs - Have made the change and will report back when results are known later in the AM.

I find it interesting the the picture you posted is actually Ascii chars all mushed together.... F0596425... seems to go on, but I can't read it.... Is this the data trying to be barcoded?

@RandyMarion Yes it is. The form previews nicely, just not printing. @DougHiggs - That seems to be a new feature in the newer version of Crystal. By choosing the change to barcode"" option, only the bar code fonts are displayed. A nice little shortcut, but not effective for me today....

New terminal server so it may be a print driver issue.

Has anyone worked with this? It is the RDP printing software in play. As I recall, we had similar issues several years back which the former IT support team resolved. Current IT person is not going out of her area to troubleshoot. http://www.terminalworks.com/remote-desktop-printing?gclid=CKvJpPzH4MkCFYEsHwodiogEPQ

TSPrint works by passing a compressed copy of the raw-document-printout down to the local workstation/printer, where it is then printed. I wonder if the barcode font is simply missing from that workstation.

Given that it prints correctly to laser and preview, I agree with @DougHiggs - I would focus on printer drivers. Lets face it, windows never handled dot matrix printers all that well to begin with...

You may try creating a new windows printer with a generic printer driver.

Or try a different emulation... IBM or Epson if available.

Time to take matters into my own hand. Amazing that IT doesn't realize that there are different emulations for OKI. Can't tell you how many times this happens to me.

Some of these young pups haven't been through the wars with the dot matrix printers.