Mous:
Your comment (thank you) triggered an idea and I made some discovers. It doesn't appear to be validation-related but rather REQUIRED FIELD related. (FYI, using LD ES4.)
After expanding the target version from 10.0 and higher to include 9.0 and higher:
- Even with all Form Validation options "off" in Form Properties>Form Validation:
- The standard "(field tool-tip or name here) cannot be left blank" messageBox is automatically being triggered by Acrobat/Reader(9,10 11) when either:
- On exit, a field fails a custom script validation and the field is cleared (for re-entry of data by resetting focus to that field); or
- The field has data when entered; data is deleted; field is exited.
- And specific to Acrobat 9 (9.5.5 is what I'm testing on):
- When the document opens, any drop-down lists that are empty are having their tool-tips or names combined into a single pop-up stating they cannot be left empty; and
- Validation scripts with commands to reset the focus to the field that just failed validation are being ignored and focus is being set to the next available field.
After expanding the target version from 10.0 and higher to include 9.1 and higher:
- Even with all Form Validation options "off" in Form Properties>Form Validation:
- All of the above is resolved except for:
- When the document opens in Acrobat 9.5.5, any drop-down lists that are empty are having their tool-tips or names combined into a single messageBox stating they cannot be left empty --- before the end-user has even done anything.
I could live with limiting it to 9.1 and higher but that errant messageBox when opening the document is really confusing. And why is it only picking up on required drop-down lists??? Attempts at renaming/recreating drop down fields have been unsuccessful. If there's a required drop-down list anywhere, it's in the messageBox.
Either way, something under the hood is triggering Acrobat/Reader to give notice that required fields cannot be left empty, even though that option is turned off. I don't think it's any of the code I've written. It's as if expanding the target version changed some internal code which is triggering Acrobat/Reader to create the messageBoxes.
While I'd rather know why this is happening and fix it organically, is there a possible work around to the problem? For example, I've got "app.runtimeHighlight = false" in the form's doc ready event to remove the red border highlighting for the required fields. Something similar like "app."auto-check for required fields when exiting" = false" ? (You get the point; something to turn off the auto-check)
Otherwise, I've also experimented with rebuilding the entire thing but any attempts to save time via fragment use, creating custom objects or even cut-n-paste are blowing up the re-build's file size exponentially.
I'd be grateful for thoughts on anything - even tricks to speed up a rebuild without blowing up file size.
Brian
