Hi K.C.To answer your question. I think I know the problem they have:When entering large numbers they might be wrongly overgiven if they are larger than 2^31.There might be aftercommadigits added or (if you forbid that via pattern) the last digit might change.So you tiptoe around that problem. You tell Livecycle that this is no number but a string. If it is treated as a string the value won't change. By using a pattern you can prohibit the user to write anything into it but a number and you can ...

This property applies only to the following scripting events: prePrint, preSubmit, preExecute, preOpen, and preSignPlease visit the link for details. http://help.adobe.com/en_US/livecycle/9.0/designerHelp/index.htm?content=001046.html

You can create a new Script Object at form-level. (Right click on the form and select "Insert Script Object")Next give the new object a proper name (e.g. GlobalFunctions)In the Script Object you can enter your scripts like you are used to do within control-event (unless you are using FormCalc as script-language, because script objects only allows JavaScript). However it is now a function instead of a event, so you need to make a function of it. E.g:function DoSomething(SomeParameter) { return "I...

Sorry, I guess I didn't fully understood your question.The changes will be maintain when you save the form. In your case option 5b would be the expected behavior.Jasmin

Sorry, you're right: it's A.