>Ken,
>
>>So why can't it just update the row that is already there? Especially for minor changes.
>
>You'd have to ask the design team that question. I suspect it's not worth the effort/time of tracking the changes in properties and methods and reserved memos to know what to update. It's easier to just delete the old records and append the new ones.
>
>>Well - obviously - but there has to be some particular set of circumstances that makes it start bloating.
>
>I've not been curious enough to track a sequence of events that makes it happen.

thanks david!