Adobe override calculations

Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.

Linked 0. Related I've tried looking this up and have had no success, but it may be to my "terminology". Any guidance would be greatly appreciated. Thank you. Peter Stewart. Overwriting a calculated field is possible,but it does require appropriate caution. The only calculated field which may be overwritten is the last result of a chained calculation.

If you overwrite an intermediate result, it may not be taken into account into the following calculations, and then lead to completely wrong or even illegal results.

That said, the less dangerous way to allow for overwriting results is to have a checkbox nearby indicating that this particular field is overwritten. Any other suggestions?

Angie, I tried your solution and Acrobat 8. I haven't tried it in Acrobat 9. Does it work there? Just an FYI, I've tried a variety of words too Nothing has fixed the issue though The only thing I've found that works is setting it to "disabled" from another script. Nope, tried that one too: Acrobat allows me to enter data, but then when I hit return it pops up an error message, "You are not allowed to enter data into this field".

And then the calculated value is restored. This is on the edge stuff. You have two situations that are directly opposed to each other, the user entering data and a forced calculated value. Which one gets presidence, under what conditions? How do you resolve it? Since there are several unclear aspects this is exactly the sort of thing that's implemented differently in different versions of Acrobat.

Hence the failure of the "ignore" value to work correctly. In situations like this, where Acrobat is whishy-washy, and there are many, I strongly recommend writing your own code that provides explicit control.

Thank you both for testing this out! I'm glad it's not just me it isn't working for! Thomp - is there a work-around code that could work for this? I have about 20 calculated numeric fields in my table, all of which obviously generate this warning. Registered: Jul 6