I have a similar issue. But based on an existing form.I am trying to populate the form from an XML data set. Like if the value of the checkbox is X in XML data then it has to fire the validation for the click event but not able to achieve that.
But it does pout a X on the check button.
quick recap of this code PAul posted just so i understand why its used at all.
Right now a for LOOP is the approached looked at by Paul but i was wondering if this approach is used because of other avenues not working well.
Here is what i mean:
i have a Page inside my form called Page 1 and on that form i have objects.
Those objects i want to lock down so what i do is this:
At the page level under initialize i put code:
And tha will lock all objects on that page down the way i want. BUT if i use this code on a txtfiled on that page that is currently locked:
Under initialize or anywhere else (event wize) :
I can not open that field at all in any way shape or form. The Page lockout seams to be to powerfull and it remains locked.
My question realy is:
Is the FOR loop apprach to locking fields individualy (rather then in one deal at the parent level) the only way to go in order to be able to manually change any radom object on that page to an access level = "open"?
because i would rather be able to lock fields down at the parent level of a collection of objects rather then individually, but maybe i just cant with LiveCycle designer???
Please feel free to ask me more questions if this is not clear, but for me, i see all these posibilities to lock objects using the objectName.access="something"; but it doesnt seam to want to work.
thank you very much,
It will not allow me to make any changes to a saved fillable form. How do I add the "lock all fields" option?
Is it still possible to get a hold of the script that was so popular all this time ago?
It would be so helpful for me!
ewan (dot) ross 1 (at) gmail (dot) com