Can you think of any reason why this code would cause some, but not all, of my insert triggers to fail? Update triggers seem to work ok. All seemed to work ok until I upgraded to VFP9.


>Hi Debra,
>
>The intent of this code is to make sure that the parent record won't be changed by another client until transaction is committed.
>
>Thanks,
>Aleksey.
>
>>I have compared the RI code generated by VFP8 to the code generated by VFP9 and found that the following block of code appears in every RI_INSERT and RI_UPDATE procedure:
>>
>>

>>if llRetVal and not (isrlocked(pnParentRec, lcParentWkArea) or ;
>>   isflocked(lcParentWkArea))
>>   if rlock(lcParentWkArea)
>>     unlock record pnParentRec in lcParentWkArea
>>   else
>>     =rireuse("tparen",lcParentWkArea)
>>     pnError = rierror(-1,"Insert restrict rule violated.","","")
>>     IF _triggerlevel=1
>>       DO riend WITH llRetVal
>>     ENDIF at the end of the highest trigger level
>>     SELECT (lcStartArea)
>>     RETURN llRetVal
>>   endif
>>endif
>>

>>
>>It is making several, but not all, of my insert triggers fail. If I comment this code in the store procedures, all works fine.
>>
>>I can't find in any documentation that the RI Builder was changed for VFP9. Can you shed any light on what the intent of this code is?