The weakness with modification date/TS is that it is completely non-specific. It tells you only that something in the record was modified, but gives no further clue. If you were to cut the contents of a field, then paste the same contents back into the field, nothing has changed in the record, but as far as FM is concerned the record has been modified. Far more useful is an audit trail, such as NightWing's Ultralog.
Thank you for the reply.
I have created two columns date columns with creation date and modification date in three tables.
When modifying the data in one table(A), the modification date gets updated which is correct.
As a result of modifying the data in table A, table B modification date also gets updated where as table C's modification date is not updated. Is the table B date column updated because of somewhere the modified field(table A) is used in the calculation of table B. Please confirm.
Changes to unstored calcs (i.e. a calc field in A changing because a value changed in B) are NOT captured by the modification auto-entry. Somewhere along the way, you're editing A as well although, as pointed out, that just means data was edited, not necessarily that it was changed to something different.