Thanks for the help. The script worked perfectly -- I added some app.alerts in various points to understand what was going on. I hadn't thought about using scripts -- that's a great idea.
I do have another issue that's arisen -- I want to use the Reader Extensions so that the users can email the completed form. After the script runs, the screen looks perfect. However if they either save the completed form or email the form, what gets saved or emailed is the form with the data, however, none of the formatting that the script applies (hiding borders, protecting fields) is in the emailed or saved copies. It's like the script never ran. I tried running the script as a preSave event, instead of on a button click before using "File, Save", but I can't add the Reader Extensions because it runs the script when I try to save the form in Acrobat (after adding the extensions)!
Why would the screen look perfect but the saved form not match the screen?
On the Form Properties under the Defaults tab there is a Radio Button that indicates whether to keep the state of the form that the script changes has done or not. Change the radio button to automatic and try it again.
Dynamic XML Form Target version does not support the Preserve Scripting Changes To Form When Saved option. Select File > Form Properties, click the Defaults tab and, under Preserve Scripting Changes to Form When Saved, select Manually."
The documentation indicates that Reader 8.0 is required. The form has to run with Reader 7.0.5. So how do I preserve the scripting changes manually/can Reader 7.X do this?
Nope ...we have to do it through script when we load. We will need to know that we have to display without borders so we can have a hidden field that will act as our flag. If we populate the hidden field with a known value when we click the button that prepares our form then we can check the status of the flag and act accordingly. The event you want to do this on is DocReady (at the form1 node) then simply: