Since there is no Acrobat Reader for Linux since 2009, you don't have an official way to view those forms on that platform. Some webbrowsers like Firefox and Chrome nowadays have XFA support, so you might have a small chance by using those. 

Since you form doesn't use a XML scheme but object names for data binding you must be very very carefully to not use the same name for multiple objects in the form, as this might result in the effect your're facing with. Make sure to give very table, every row, every field an individual name. 

It's not possible. The attachment get's named by the form. To change the name, you'll hat to save the form with the desired one first. 

The debugger says, it's a Folder-Level script. So the script you're looking for is not placed in your form but in a js-file saved on your computer. Look into the Javascripts folder of your Acrobat:  /C/Program Files (x86)/Adobe/Acrobat DC/Acrobat/Javascripts

There's another method with floating fields, which you can edit directly in the static text. https://web.archive.org/web/20101124093614/http://blogs.adobe.com:80/formfeed/2010/09/editable-floating-fields-v3.html

Don't call the relayout() method from a change event. Your form can become unusable slow then. The relayout takes place, once the rawValue is set to a field which happens when you exit it. XFA forms are not designed to expand fields while typing. 

The option "Repeat Row for each Data" has nothing to do with this. The cell, row and table have to allow page breaks. However, there are conditions with nested tables, where it won't work properly. If you can share the form, we can look into it.

With the typical keyboard layout you only get straight quotes, the curly ones are only accessible by entering their character code with the additional number keys on the right. It requires some discipline but you're getting used to.  Here's a great ressource, that explains it and many other things a...

You'll have to use resolveNodes() and a loop to update all instances of the buttons. The method resolveNodes creates a nodeList you can process. Use the accessor [*] to tell it there are multiple instances to resolve. To a resolve a spicific instance use the index number instead of an asterisk. If y...

It might be better to decouple methods that rely on the speed of external ressources or users. So instead of using one event to execute all of them use several. Put the part that happens after the submitting into the postSubmit event of the form or button and wrap the messageBox in an if-statement t...