Avatar

Level 10

Cameron,

There are a number of factors that can influence the processing overhead required to perform barcode encoding. I assume you are referring to the PaperForms barcode and the PDF417 symbology. This list of factors is not inclusive.

1) XML kills. Avoid using XML formatting.

2) Use single case. The PDF417 encoder spec (not the Reader/Acrobat implementation of the spec) has to encode a character indicating case switching each and every time it encounters a case switch in the data being encoded. Punctuation in the form text introduces the same issue.

3) The use of the compression option increases processing time and can actually reduce data capacity. The compression ratio is highly dependent upon the characteristics of the data being encoded.

4) The complexity of the form and the method for accessing data to be encoded in the barcode. A form with dynamic subforms and tables may require xfa.resolveNode() to access data. This is unavoidable and will influence performance.

5) The number of form fields and the number of events associated with the form fields. A lot of calculate and validation events is going to influence the general performance of the form (and may be hard to avoid).

I would discourage moving barcode encoding from the barcode calculate event. It introduces the likelihood that data will not get encoded.

Steve