Hi Geoffrey,

>It might, if it's open exclusive, though I can't see why.
>
>It certainly appends any changed memo field. We studied this a few months ago, in comparison with Codebase. Codebase does a replace when the changed memo content is not greater than the current content. I find it hard to believe that MS has not done the same.

I don't know for sure but I would bet that it has something to do with record locking.

>As for the main topic of the thread, it is currently necessary to know the status of deletes in order to select the appropriate option. My grudge is that I have a control file with one record (never deleted), but a memo field in which I log certain events. Even if one clears the logged content, the FPT tends to grow to enormous size. SDT doesn't fix it - one has to specifically pack memo.

I'm with you on this one. However with only one record you can use text file instead of memo field. It'll give you full control over its size. The STRTOFILE() and FILETOSTR() functions make manipulation of the text file easy.

>The code required to implement the replacement option in codebase is only a few lines. A cool refinement would be to also not append if the memo to be updated was the last entry in the fpt. Not worth the effort on its own, but easy to implement in conjunction with replacement.

Yes, it would be nice improvements.