On Feb 17, 2009, at 11:43 AM, Chuck Pelto wrote:
Is there ANYWAY automated way to get around the prohibition against
using global or related field data and still have an indexed calc
field? I mean other than using REPLACE or LOOKUP?
It depends on the behavior you want.
You can always use an auto-enter calculation, with the "Do no
replace..." option unchecked. When configured in this manner, the auto-
enter calc behaves just like a normal stored calculation field does.
However, it doesn't make global or related fields behave any
differently. That is, you can include these field types in you auto-
enter calculation but changing the global or related value won't cause
your calculation to update. For example, with an auto-enter
calculation formula of:
Field1 + gField2 + Related::Field3
the only field that will cause the calculation to update is 'Field1' -
changing the other fields will have no impact on the calculation value.
(Actually, to be precise, global fields do have an impact but the
rules are somewhat complicated and make the behavior appear
unpredictable.)
Cheers,
-corn
Corn Walker
The Proof Group
http://proofgroup.com/
