>>>Hi,
>>>I have an issue of memo bloat. I'm concerned that if I change the default 64 to 0 it will cause issues with the program. But I have do something soon. Daily the fpt file grows 10 fold - 103000 before and after 10000 bytes - after a pack memo.
>>>
>>>So does anyone have a history of making the change?
>>>
>>>John
>>
>>John,
>>
>>When a new memo is added or an existing is changed the blocks are allocated in 64 byte chuncks, so on average there is a waste of 32 bytes/memo
>>Changing a memo does not happen 'in place', the whole memo is rewritten, the old apace is not re-used, hence the bloat
>
>This is not true, if LEN(memo) it doesn't overcome CEILING(LEN(memo)/BLOCKSIZE)*BLOCKSIZE
>blocksize it rewritten the memo in place.
>


I was under the impression that it was always rewritten. Is this recent or has it always been like that ?
Then John's setting of 64 is better than 0 if there are a lot of replaces done



>
>>setting the block size to 0 will get rid of the 32 bytes waste/memo, so there'll be some gain
>>
>
>>What you are experiencing is imo a bloat due to a lot of replaces or delete-insert and setting the block size to zero will not improve much.
>>
>>As to your concern, all my memo fields have been created with block size 0. I have not had any problems with that
>>
>>So, it's worth trying. Just don't expect too much of it