That is the default, yes when this feature is enabled. However, if the highlight existing fields feature is enabled in Acrobat, you will see red borders. The designer feature will turn this off by default via script added to the form, but it may be that it has been reenabled by clicking on it (?). I...

Look at using the form validation feature in Designer. It will disable the Acrobat Highlight fields feature, which automatically shows you all the mandatory fields on a form.

Has the schema actually changed? If you generated your data connection using an XSD schema, the XFA data description is dervived from this and is cached in the XDP. If the source XSD has changed it will no longer match the data description stored in the XDP, and you will need to refresh your data co...

the data source name needs to be IDP_DS in WAS 7's JDBC resources, not S_DS.

Glad to help and see you passed the issue!As you have just dicovered, with automatic or implicit binding (Use Names), 'like' names are significant, whereas 'unique' names are not in the binding process. Cheers, KJ

Consider the following scenario: if you have defined a table and made a Cell in the table contain a TextField and it repeats, the SOM expression would look this form1.Table1.Row1.TextField1[0] (Cell1 of Row1) as an example. This instance of TextField[0] can be captured in the barcode Collection via ...

Sorry. did you or did you not reproduce this with a simplified version of your form?Reader will interpret the initial design layout as you see it in Designer, unless altered via script at runtime.I cannot reproduce what you are claiming in a simplified sample. I suggest logging a ticket with Adobe E...

I'll admit, I am confused by your result as well. You shouldn't have to set the initial property to make this work.I am using Designer 10 (ES3), and am Rendering the XDP to PDF in Acrobat 10.1.3. Perhaps it is the reader version here?Can you share your form on acrobat.com?

Yes, for the "save" issue now that I see the form, I would try Kevin Mortimer's suggestion. The binding is "automatic" for all the subforms[0..23], meaning we will use the name of the object to merge the data with. Like names are significant, where as unique names are not.When you reload the form, a...

Ken, This sounds like a tabbing order issue. Please review your tabbing order. It is possible that if you have a dynamic form, and you add a new instance of the subform at run time, the tab order does not know where to go now once you leave the last field in the subform, and geographic tabbing order...