Hi Walter,

I think, I read in the same thread (or was it the other one?), that your RI builder doesn't handle NULLs. And it uses macros, which would made it unusable with Ole Db.

I'm going to create a new thread with everything we discovered so far about RI builder.

>Hi Nadya,
>
>I really don't know from the top of my head TaxRi does handle .NULL. values right. You'll have to try. If not, give me a note then I'll try to fix the problem.
>
>TaxRi, however does have an insert RI rule "allow blank". Not exactly the same, but I could adjust the routine fairly easily to let it mean that it accepts .NULL. values as well.
>
>Walter,
>
>>>Hi patrick,
>>>
>>>I never was able to determine the exact cause of the problem. In my case it 'seemed'to have something to do with doing a TABLEUPDATE() on a row buffered table twice within one transaction. I eliminated the second TABLEUPDATE() and the problem seemed to have disappeared.
>>>
>>>I would not be surprised if it has something to do with RI code attached to the table. Are you using triggers (for RI or other purpose)? If so, are you using TAXRI or the default VFP RI builder?
>>>
>>>Thanks,
>>>
>>>Walter,
>>
>>I'm having the same problem. I know, what I have a trigger failure. This RI_Handler has a bug: it does not allow to insert nulls if we have restrictions. Does your TaxRI allow NULLs?