>>>>>>Glad my question prompted you to check the view.
>>>>>
>>>>>But no...that didn't work...i was SURE it was the problem..hmmmmm...got the same thing....the view now DOES def. update the SER_lVoid field.
>>>>
>>>>When you insert a new record into the view - is this new record unique (e.g. these 2 IDs don't yet exist in your actual table)?
>>>
>>>The error is on the TableUpdate()...all the entries have been added to the view...see attached.
>>
>>BINTOC(SER_CLINICFK)+BINTOC(SER_INVOICE)
>>FOR NOT DELETED() and NOT lVOID
>>
>>This means, you can have only one record for the same SER_CLINICFK and Ser_Invoice which has lVOID = .F.
>
>Right...i believe that is the case here (UNLESS I'm missing something, which very well could be!)..there is a single record for:
>SER_ClinicFK = 820
>invoice = 1
>Void = .F.
>
>the other records have Void = .T.
>
>>
>>Also, does it let you save the data if you don't add the very last record?
>YES! huh! it allows the multiple VOIDED entries to be imported. hmmmmm....

Check in the table itself if you already have a Void = .f. record for that clinic. Check also using SET DELETED OFF.