>>>>(1) Can you replace the name of the current trigger (say __RI_update_customer()) with __RI_update_customer() and MyTrigger(). This has to be done each time you rebuild the ri.
>>>
>>>It doesn't have to be re-done. The RI-builder will respect (maintain) the part starting with "and".
>>
>>Hilmar,
>>
>>To be honnest, I have never tested that part since I have not used the vfp built ri for a long time.
>
>I am curious - what do you use an alternative?

I have made my own. The ri code is not resident in the database, it is in the exe and the table triggers call routines in the exe.

Advantages. No one can change anything in the db (with ODBC say) and it is easy for maintaining, just put another exe/app on the site

I wanted a bit more of functionality, it basically looks like this

TriggerRoutine(TableName, TriggerType)

    && do some routines before RI checking, failure exists with FALSE
    && the routines are customized, and involve mostly checking beyond basic RI

    && do the RI, failure exits with FALSE

    && do some other routines after RI checking, failure exits with FALSE
    && here we may update other tables

The TriggerRoutine() is only one program which is table driven. The tables are loaded into an object model when you open a db

Another advantage is that all the logic is in one place, no matter where the table is being modified

But then, had I known what you have written, it would have saved me days of work (but less fun)