Hi Tim, Thanks!
Let me just check whether I understood the logic behind it. This scheme seems to assume that when a formula goes through a one-to-many link to fetch a value, it will only see one record at the target panel, namely the first one in the index, which is why we use the reverse date index. Is that correct? > Unless you absolutely have to use it in an index, you should > make this 'Cost of most recent purchase' field in the > Inventory panel be a "computed value field" using the ::C > field format suffix (i.e. something like G$ZZZ,ZZ9.99::C). > This makes the field formula get calculated whenever you > display or access the record so that it always has the > correct value. Otherwise if the field is a "real value" field > (without the ::C), it only gets updated whenever a change is > made to the record. I do want to use it in an index, because the "Inventory" panel must send the value of the 'Cost of most recent purchase' field (among others) to a third panel, "Merchandise Sold", via a data link. It is alright if the 'Cost of most recent purchase' field only gets updated when a change is made to the record. The shop owner would not want to update this field unless he actually made a purchase (and the cost changed), in which case he would have to update the record because of the 'Quantity of items in stock' field. Thanks! Marcos _______________________________________________ Dataperf mailing list [email protected] http://lists.dataperfect.nl/mailman/listinfo/dataperf
