>>Blocksize 0 is not a good idea.
>>
>>To further explain....
>>
>>If you edit an existing memo and the new data can fit in the existing allocated block, it will be used. Only if it is too big will it allocate new blocks. So, with blocksize 0, space will be allocated EVERY TIME you edit a memo. Even adding a new memo could cause huge bloat issues.
>>
>
>Unfortunately it's only true for tables opened exclusively. For shared tables FoxPro always allocates new memo blocks so Blocksize 0 is a good idea

I had forgotten that! Thanks for the reminder.