>Can you mark those carrier records as 'no longer used?' That is what we do.
>

Through the program interface we have an ability to Merge two carriers together. Then one becomes inactive and all records get re-pointed to this new merged Carrier instead.

See my recent thread about a problem I'm facing.

I found that I didn't have code to deactivate Address and Phones records when I merge two Carrier Branches together. Now, it means I have to create a separate CA class for Address and Phones and a separate BO class for Address-Merge and Phones-Merge. I don't see a simple way around it because alias name and parameter name are fixed and I don't know if I'll get into much trouble trying to make them variables. Perhaps I better do create a complete replica of my existing classes using different alias and parameter... Or I can try to use subclass...


>>>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.
>>>
>>In our system we're not deleting records at all. We only make them active/inactive. However, we have some garbage records in our Carriers table. I was thinking we can get rid of them, but then realized we have too many dependencies...