Just curious based on your last comments Naomi. We work with insurance records (our app is an agency management system) and we have to retain policy records for 7 years until after the close of all claims, then we can dispose of them. We archive old policy records, claims, and data.


>Good. I already realized, that removing Carrier is not that easy. If we have insurances pointed to the Carrier Branch that points to the bad Carrier, it means than we may have transaction pointing to this insurance. In other words, we probably should never delete Insurance records in our system. Also Carrier Branch may point to an Address and a Phone record, so if we delete Carrier Branch we would leave orphans in these tables. I would probably have to update my local data tomorrow using our network copy and I'm going to send an e-mail to my manager that I was wrong and we should not try to get rid of the bad Carriers...
>
>>I usually run SELECT with the same conditions and check result to see if it does what I want.
>>
>>>I want to delete all bad child records in Insurances for empty Carriers or XXXXXXXX Carriers. I do
>>>
>>>

>>>DELETE FROM Insurances where cCarrier_Branches_fk ;
>>>in (select cCarrier_Branches_pk from Carrier_Branches ;
>>>inner Join Carriers on Carrier_Branches.cCarriers_fk = Carriers.cCarriers_pk ;
>>>where EMPTY(cCarrier_Name) ;
>>>OR 'XXX' $ cCarrier_Name)

>>>
>>>I then checked number of deleted records and it's too big (but I didn't check it before running this code). Am I right here?
>>>
>>>Thanks.