Optimistic row buffering, Vlad. For some reason the SEEK is calling the Referential Integrity code, 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.

Thanks,
Barbara

>What type of buffering are you using?
>
>Vlad
>
>>Rule and Trigger Code must balance transaction usage. Full help text:
>>
>>A rule or trigger expression, or code invoked from an expression, has either started a transaction that it did not finish or finished one that it did not start. The write attempt that fired the rule or trigger code has been aborted.
>>
>>I have a client who is getting this message on a SEEK. The table in question is loaded by the form, user types in a value to a text field that has no control source, and I do a SEEK on this value. The above error appears, followed by other errors such as "Record is in use by another user" and "Invalid Seek Offset" as I try to quit gracefully.
>>
>>No code is being written to disk, no updates to the table have been made, I've re-written both the form and the code to no avail. We've re-indexed the files. No change.
>>
>>Any suggestions?
>>
>>TIA
>>Barbara