"2.4.9 All calculation fields that return text, number, date, time and timestamp results can be indexed."
This is false. If the calculation refers to a field in a related table, or a field with global storage, the field will always be unstored and unstored fields cannot be indexed no matter what the data type.
Thanx for your prompt reply. That was a tricky one I guess. Calculation fields that return text, number, date, timestamp results can be indexed BUT NOT ALL.
I have heard this comment before about this exact question. As Phil notes, it is important to carefully read the questions in the book and also in the exam. The important word in this question is "All". Interesting rule of thumb from Phil :)
From a trainer's point of view, the question is what are we trying to assess here? IMO we are trying to assess what are the limitations on being able to index a field? Obviously, one limitation is the field or result type - container fields cannot be indexed. The other limitation is the source of data in a calculation - related, global and unstored make indexing impossible.
In the end, it might not be the best question but what I would like to point out here is a tip for studying - look beyond any question and ask what the assessor is trying to test. If you do that, you will be able to come up with other questions of the same type that are useful in testing your knowledge. :)
TS_Oz, FileMaker Inc.
Again thank you very much. This comments are also very useful to tackle in general a future test.
I also wanted to add that the training series are in English and my software is in French and my mother's tongue is Spanish so the languague, sometime is tricky and may become a handicap. I guess many others are in my situation. This forum is great to tackle this issue a per the previous answers. Thanx again.