>>>That would be a good idea, however I do not have a DBC. It is a very old database from FPW26 converted and it would be too much work to add a dbc.
>>
>>I did sopmething like that in the old days. Having an index with a filter on a function. That function evaluates whenever a change is made in the record.
>>The function set a boolean field to .T. to indicate that a change is make. the trick is to make sure the function is available (preferably a PRG) whenever you make a change.
>>
>>Walter,
>
>That is a good idea, I could set a timefield value and then the process could check which records were updated, so the update could be more specific.

On an old system we also added a table echoing changes across all tables - querying this table informed client, which tables might need to be re-queried. Depends a lot on your use case ;-)