Hi, The print method requires eight parameters. The second parameter "0" is the start page for the printout, using a zero-based numbering system. Eg "0" is the first page. The third parameter (xfa.host.numPages -1).toString() is a calculation for the last page to be printed in the range. It calculat...

Hi Karl,Here is your form back to you: https://acrobat.com/#d=oRRJP3W*OgBk6DqXXbJhgg. I have corrected the Add button, the Delete button and the Delete First Row button. I have annotated the script, so hopefully you can follow it. Hope that helps,Niall

Hi,I can't check out your form now, but I have an example where the one set of Add/Delete buttons act on two tables: http://assure.ly/eTOXaH.Hope that helps,Niall

Hi,The problem is the event that you have used. The initialize event will fire when the new instance of the repeating object is rendered. Therefore the script fires repeatedly. If you need this to fire when the form is opened, try docReady (with an if statement I suspect). Otherwise elaborate on why...

Glad you have it working Shaun!As you know == and != are testing equality and inequality. These work very well when testing conditions, it can be useful to test for identity (===) or nonidentity (!==). These operators are testing that the two values are identical. This means that not only are you te...

Okay Shaun, I have updated the example to deal with objects to be excluded. This is as outlined above. The updated example is available at the same link (http://assure.ly/MzX1bK). Hope that helps,Niall

Hi Shaun, There are a couple of things here, so I'll try and take them one at a time. Do not process certain fieldsFor this I would have the start of the objects that you do not want processed, to have names that start with a set string. Like "DONOTTESTtextfield1". Then the else if statement becomes...

Hi Shaun, Yes, default values and objects with script that set the rawValue, will satisfy the !== null and therefore will allow the page to be printed. To get around that you would need to name these objects specifically AND then amend the function to test for the object name. For example, name the ...

Hi Shaun, Yes, this should still work as the overflow page is still just an instance of page1. Good luck,Niall

This is just to test out the code block. // Hide the pagethis.presence = "hidden";// Call the functionAssureDynamics.CheckForNull(page1, page1);Niall