I have created a 2d barcode form in designer 8 the form is a two page form with four barcodes to capture the data. The barcodes are on the second page. The form works fine if you open it in Adobe pro but slow down and you see the hour glass appearing once you move the mouse over any field when it is open in reader. I have saved the form with no embeded fonts. Is there a setting i am missing for the barcode set up.
If you are using the automatically generated code then this may be because each one of the barcodes is being updated after each modification by the user.
The default code is placed in the Calculate event. You may want to consider moving this to the pre-print event or use custom code that addresses each one of the fields directly using something along the lines of
Of course, you would add the other values you require in the barcode.
Again, roughly translated the above code basically says: "my value is equal to the value of the Consideration field, a tab, and then the value of the Parent field, and another tab.
Another item you may want to reconsider is the field name values. Your field names are fairly long in some cases and including them in the barcode will reduce your capacity. In your "Section3" the field names may actually be longer than the data they hold.
Hi George, if you want to add field names you can again, do it manually with script but again, I would suggest against it because of the space requirement in the barcode.
The BIG concern I have with your response is that it sounds like you are going to use the SAMPLE workflow agent that comes with the Adobe LiveCycle Barcoded Forms for Ascent Capture installation. This is a SAMPLE only and should not be put into a production environment without modification. If you look at the source code that comes with the sample (VB 6 code I believe) you will see there are absolutely no error capture routines, exceptions, or anything other than a straight data translation routine that populates AC index fields.
You really should not use this sample without making the required changes to it that you need for it to work reliably in your production environment. The sample works well as exactly that - a sample.
Kofax did send us some error checking to put in the code see below.
But when I tried it with the raw.Value without the field names it goes to one field that thats takes all the data. The workflow does not put the fields in the AC index fields because there are no field names.
What will I need to do to modify the code.
This is really getting very difficult and I have a deadline. Is it possible to do the connect web session as you suggested.
*****Kofax Fix that was sent*****************
The fix for this is to modify the sample Workflow Agent so that it ignores
these blank fields in the tab-delimited output:
For i = 0 To (iBarcodeFields - 1)
If FieldName(i) <> "" Then
Set oIndexField_Field = _
If Not oIndexField_Field Is Nothing Then
oIndexField_Field.AttributeValue("Value") = FieldValue(i)
A check is added (the first If statement) to see if the current field name is
an empty string - If not then process the field.
What is causing the form to move so slow when you use the automatic scripting on the barcode than when you use the custom scripting.
Because the collection sets seems a nice tool to use. I did not plan on doing much coding that why I tried ver 8 to assign to fields to diferent barcodes.
If you do have additional scripting questions or barcoded forms questions, feel free to join me on Monday September 24th at 1:00pm Eastern in this Acrobat Connect room: http://my.adobe.acrobat.com/barcodedforms/
Dial-in information will be provided once you enter the Connect room.
I am getting the word "NULL" appearing in emplty fields not filled out on the form when the 2D Barcode Forms is decoded in Ascent Capture 7 using the Adobe 2D Bsrcode Acsent Capture module. This happens when I used the custom scripting instead of the automatic codeding.
Inside your custom script you will need to ensure that fields are not "null" before putting the data into your script. You can do this by checking the fields on the exit of the field or running through the fields prior to updating your barcode.