ReportBuilder's support for the Code 128 barcode symbology can be used to print UCC\EAN 128 barcodes. Code 128 is general purpose symbology that can be used to generate UCC/EAN 128 barcodes.
1. Here is a link that came up when I searched in Google. It is for another barcode product, but it explains the symbology.
2. The TppBarCode component contains an AutoEncode property that defaults to True. To support UCC/EAN 128 you will need set AutoEncode to False and manually encode the data. See the AutoEncode topic in the RBuilder.hlp. From there you can access a related topic on manually encoding Code 128 data.
I solved this as per this post 4/1/2003, but this quick fix does mean any code128 comes out as ean128 which was fine for me. Hopefully RB's shift also gives them more resources to work on such things?
I made the following change to the Code128 Autoencode procedure in ppDrwCmd.pas to get it to do EAN 128 ( It's just got a FUNC1 char as the second character ) and it works fine. After reading another post that it was not recommended to recompile the packages, I followed that posts instructions and just copied the file ppDrwCmd to my application directory. However this means I had to turn packages off. Can you instruct me what package to rebuild and any issues I might encounter doing so. I also look forward to seeing a official EAN 128 support next maintenance release.
Comments
Tech Tip: UCC/EAN 128 Barcode Generation
--------------------------------------------------------
ReportBuilder's support for the Code 128 barcode symbology can be used to
print UCC\EAN 128 barcodes.
Code 128 is general purpose symbology that can be used to generate UCC/EAN
128 barcodes.
1. Here is a link that came up when I searched in Google. It is for another
barcode product, but it explains the symbology.
http://www.idautomation.com/code128faq.html#EAN128andUCC128
2. The TppBarCode component contains an AutoEncode property that defaults to
True. To support UCC/EAN 128 you will need set AutoEncode to False and
manually encode the data. See the AutoEncode topic in the RBuilder.hlp. From
there you can access a related topic on manually encoding Code 128 data.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
code128 comes out as ean128 which was fine for me. Hopefully RB's shift also
gives them more resources to work on such things?
I made the following change to the Code128 Autoencode procedure in
ppDrwCmd.pas to get it to do EAN 128 ( It's just got a FUNC1 char as the
second character ) and it works fine. After reading another post that it was
not recommended to recompile the packages, I followed that posts
instructions and just copied the file ppDrwCmd to my application directory.
However this means I had to turn packages off. Can you instruct me what
package to rebuild and any issues I might encounter doing so. I also look
forward to seeing a official EAN 128 support next maintenance release.
Regards, Phillip Herries
procedure TppDrawBarCode.AutoEncode128(var sData : string);
const
CharSetA : set of char = [' '..'_', #201, #202, #206, #207, #211..#242];
.
.
StartC = #210;
TempShift = #203;
Func1 = #207; // for FUNC1 code
ControlChars : set of char = [SwitchA, SwitchB, SwitchC, StartA, StartB,
StartC,TempShift,Func1]; // included Func1 code
.
.
.
sData := S;
Insert(Chr(207),sData,2); // insert FUNC1 as second char.
end; {procedure, AutoEncode128}
Also got another reply re the packages issue as per below...
section of any units, you can simple recompile the one affected packages, in
this case rbRBC7X.dpk.
Phillip Herries