February 25, 200916 yr Is there anything wrong in using an unstored calculation field within another calculation? I have a database that is used to print barcoded container labels. In this database, I have a quantity field and an external function that uses a calculation field to create the barcode. One of my customers requires leading zeros for the quantity field. To accommodate this requirement, I created a calculation field, qty_8_chr, that is an unstored calculation: Right ("0000000" & qty;8) The barcode calculation is Barcode(qty_8_chr,1,0,1) It seems to work properly, however, I wasn't sure if this is good practice? Any advice?
February 25, 200916 yr If that's the only thing it's needed for, why not make the barcode calculation = Barcode ( Right ( "0000000" & qty ; 8 ) ; 1 ; 0 ; 1 ) and eliminate the field?
February 26, 200916 yr Author Well, I need a "human readable" portion above the barcode, so I need a text field to display "0000018". My current qty field only displays "18".
Create an account or sign in to comment