>>Optimistic row buffering, Vlad. For some reason the SEEK is calling the Referential Integrity code,
>
>In row buffering, the triggers are fired each time you move the record pointer into a table. SEEK moves the pointer, so the RI code is called.
>
>> and it's bombing at the client's site, although not on my system. I have a work-around now, but I'm concerned about the data. I'll suggest Glenn's total CDX re-build. And good backups.
>
>You may also take a look to the RI code and see if it's correct (the one at the client site). Maybe somebody played with it and changed it.
>
>A bad index can also brake the RI code, as Glenn already said.
>
>Vlad

Thanks, Vlad.

Barbara