1] I had read about "moduleWidth" and "moduleHeight" but only in context of 2D barcodes.But it works fine on 1D barcodes also:Go to XML Source and add the "moduleWidth" attribute to the <barcode... ...> element, eg:<field name="Code128BarCode1" w="140.11mm" h="13.594mm">  <ui>    <barcode type="code...

We use code128 symbology considerably and the options for this in Livecycle seem a bit strange.There is this property 'Data length' which appears to adjust the density of the barcode but in an 'inverse manner':Usually one specifies a 'module width' - which is the width of the thinnest constituent of...

Thanks for this,I was just reading in a "best practices" document about Livecycle which happens to give an example of a multiline table and the first thing it says to do is use nested subforms to emulate a table.So whether subform sets are used or not, it seems that the main point is "don't try to d...

Today I found myself with this problem in another area.I went with a different workaround that requires no scripting:1] do not create any table section and just stick with 1 body line in the table2] wrap each cell object of the table line in a subform [so the subforms become the actual cell objects]...

It feels so dirty but for now I've gone with a kluge:In body-line 1 I took 1 of the existing text fields & wrapped it in a subform. I then added another text field in the subform, bound it to the data element I need & made its presence hidden.In body-line 2, I have a text field and used the Initiali...

My general understanding of data binding is "vague" at best but currently I am struggling with a table that should have multiple body-lines.As best I understand it, the binding for the table of data is made against the body row, NOT the table.This then causes the rows to repeat for each row in my XM...