The [+] symbol is an indicator of fields that there isn't enough space to display its entire content. You can't control it it's visible or not. Just make sure the fields are big enough for the content. To deal with those trailing spaces, you can use a script in the fields exit to get rid of those.  ...

The bacode hasn't been designed to be editable in all that way. You can controll it's width, silence zone, aspect ratio of the moduls, the error correction level and color. Everything else is dynamically generated depending on the input data, which hast to be a string. Binary data isn't supported.  ...

For a quick edit, you can use a trial version of Designer for 30 days.  The trials serial is 1139-1001-3886-4854-1284-1828.

Hi,    surprise! Today, I'm facing the same issue but not with Acrobat DC. So, I guess it's not the app itself, that causing the problem. It may be a DLL that's being used for this process but doesn't belong to Acrobat itself. Do you know exactly when you've Reader-enabled a form? If yes then please...

I only know this from situations where the form is accessed by another process that Acrobat which prevents saving. Maybe the Windows Explorer preview or some hotfolder service.    Did you see this problem with all files or just a particular one?

Well, from your information I assume Design.tablesf.Table2.Row3 has just one occurence. You can probably control the presence of the row with this script in the layout:ready event.    var bHasDiscount = xfa.record.FormPurchaseOrder.PriceAndTax.resolveNodes('PriceComponents.[Description.value eq "Ove...

Hi,   okay, but still not detailed enough.  Is tablesf, Table2 or Row3 repeated for each data item (PriceComponent)? 

The script doesn't make clear, how the form is build.  Where does this execute from? Might be a field, but where exactly is it located?  Also, what type of field is "Description", a static text or a field?  Finally, Design.tablesf.Table2.Row3 is another table in the form with just on instance of Row...

Changing a fields presence from its enter event is a oneway as you can't make it visible again once it got hidden because the event will only execute when the field is visible.

Use the exit event of the dropdown where the user is supposed to make an selection. Chapter_Officer.presence = this.isNull ? "hidden": "visible";   Btw. You cannot use objects names that begin with a digit, since this isn't allowed by XML standards. A SOM expression as Chapter_Officer.0.0 can't work...