|
Did this same printer print POSTNET before the change? POSTNET is a very special barcode - not all printers support it. Just because a printer can print say, UPC or 3 of 9 does not mean that the printer can handle POSTNET. To debug this, I'd try to find the page that the error is occurring on and look at the source data for that record. POSTNET will not accept any hyphens or special characters, only the digits 0 through 9. Buck Calabro Billing Concepts, Albany, NY > -----Original Message----- > From: Dan Rasch > Sent: Friday, May 07, 1999 12:11 AM > To: MIDRANGE-L@midrange.com > Subject: Bar Code check and Mainfrane equivalents > > > When recently asked to modify a print file with bar codes (the type the > post office uses, called PostNet) - the print file had this error > message: > > WRITER PRINT1 found bar code check > > device PRINT1 detected an IPDS bar code command that was not allowed or > not supported by the printer. The device error code is 041100. > > The problem is not the printer, as another bar code job is working fine. > We tried to look at the printfile data using CPYSPLF but that is not > allowed for printfiles with barcode data. Does anyone know how to debug > this problem? One hint I can add is that the barcode was expanded from a > 5 char zip code to ZIP+4. I suspected it was stepping on another field > within the line, so I removed all other fields and still had the error. > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.