>I have some ideas which I'm going to implement.
>
>Do you know if there is a way to determine inside the trigger when it's the last record to replace, if, say, we're using replace next 500 command?
>

This is the true limit of VFP;
it don't support table based update index/rules/triggers;
without a event that it is fired after a table write operation,
you cannot aggregate the operation's records into a single and efficient code.

Every operation is record based.
In MS SQL the operation is command based.
An classic example is if you define an CANDIDATE index ,
makes a UPDATE that during the operation it does not respect the index ,
but to the end the table's data respects the index (ex. swap two keys ):
- VFP shoots an error
- SQL does not shoot an error

I think impossible to make it in simple and reliable way.