I have a number of computed fields whose formulas are the field’s name. For example, fieldname is “Sales_2006” and the formula is “Sales_2006”. This has worked fine for many years.
Recently, the values in these fields has changed, in many cases, to:
2.2525263426E-23
and in some cases to
-2.3450278399E+113
Any ideas why this might be happening? Also: is there a reason why self-referencing fields is not an acceptable practice?
Thanks for any help you can provide on this. A lot of data has been compromised.
Subject: RE: Value in Computed field changes
Fields, even computed fields, do not change value for no reason. Something happened to change them.
It is not good practice to have a computed field whose formula is itself, because this is a pointless calculation. You get better performance by using a “Computed when composed” field. However, I don’t see why this would cause the problem you describe.
Clearly, these fields must be getting a value from somewhere other than their own computed formulas, or they would never be anything but blank. So there is some code you’re not showing us. Whatever this code is, you have to look at it, debug it, see what it’s doing. See also the C R I S P Y document to find out what information you might think about posting to get better help with this.
- Andre Guirard, IBM/Lotus Development
Useful blog: Best Practice Makes Perfect