I used to buy commercial ISBN and UPC bar code generators but you can do all that for free on the internet now. I'll google it.hi-
need to generate a 36char barcode from a txt or xcl/xlcs file. any recommendations? prefer to have a template that references a datasource/file location.
I didn't know anything about barcodes until my customers started demanding them. The learning curve was all of fifteen minutes. The check digits prevent error, so you might find that the standard tools are all your users need.trying to make this as easy as possible for non-tech savvy enduser...but thanks.
HOLY SMOKES!!!!!!! I think this is the first time I ever remember seeing C-Scow post in the filthy chum of GA! I should have remembered that you're the king of this industrial automation stuff.Install a free Code39 barcode font, such as this from IDAutomation.
For low volume printing, configure Excel with a data link to your text, SQL, or other data source. Column 1 = human readable data (any font), imported from data source. Column 2 = Column 1 but set to the Code39 font, i.e. so the user sees data in one column, barcodes in the next. The user then selects and prints the barcode column.
If requiring production volumes, a small, simple print app (any language, applying the same Code39 font) can replace the Excel, making things even easier for the end-user. Main advantage is the ability to add lookup, batch, reprint, or similar features without requiring the user to know much more than how to click a mouse. That aside, either approach works.
Print and test a sample barcode, starting with a shorter length (10 chars perhaps). If it fails to scan properly, concatenate single asterisks before/after the actual barcode data (i.e. *data* ), reprint, retest, and all should be well. Then move on to test the full 36 characters, which is longer than any I recall printing in my own work. If you have troubles scanning and the project allows, break the long single barcode into several shorter barcodes (Part, Serial#, Rev#, MfgDate, etc). True, somebody will have more barcodes to scan...but possibly with better reliability, depending on the quality of printer, scanner, and person doing the scanning :blink:
Post back if IDAutomation's font has problems. If necessary, I can find the original source of the freeware font I use at work (possibly IDAutomation's, but not sure).
Granted, if I would have responded before having one O'Fallon 5-Day IPA's, I would have delivered a more appropriate JIT response...HOLY SMOKES!!!!!!! I think this is the first time I ever remember seeing C-Scow post in the filthy chum of GA! I should have remembered that you're the king of this industrial automation stuff.
You're losing me, Duncan. What exactly is the intended application?now im just wondering how to distribute it
:lol: :lol: :lol: :lol: ya rightmarachel said:Here is a barcode image generator for barcode 128, have a look.
HEY! I resemble that remark! :angry:HOLY SMOKES!!!!!!! I think this is the first time I ever remember seeing C-Scow post in the filthy chum of GA! I should have remembered that you're the king of this industrial automation stuff.Install a free Code39 barcode font, such as this from IDAutomation.
For low volume printing, configure Excel with a data link to your text, SQL, or other data source. Column 1 = human readable data (any font), imported from data source. Column 2 = Column 1 but set to the Code39 font, i.e. so the user sees data in one column, barcodes in the next. The user then selects and prints the barcode column.
If requiring production volumes, a small, simple print app (any language, applying the same Code39 font) can replace the Excel, making things even easier for the end-user. Main advantage is the ability to add lookup, batch, reprint, or similar features without requiring the user to know much more than how to click a mouse. That aside, either approach works.
Print and test a sample barcode, starting with a shorter length (10 chars perhaps). If it fails to scan properly, concatenate single asterisks before/after the actual barcode data (i.e. *data* ), reprint, retest, and all should be well. Then move on to test the full 36 characters, which is longer than any I recall printing in my own work. If you have troubles scanning and the project allows, break the long single barcode into several shorter barcodes (Part, Serial#, Rev#, MfgDate, etc). True, somebody will have more barcodes to scan...but possibly with better reliability, depending on the quality of printer, scanner, and person doing the scanning![]()
Post back if IDAutomation's font has problems. If necessary, I can find the original source of the freeware font I use at work (possibly IDAutomation's, but not sure).