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.



>Thanks for all the replies
>What I didn't understand is where the bloat is coming from and the entries in the table, including the memo fields, are not editable by users. Also out of 900,000 records the number of deleted records are 8-10 so the bloat is not coming from there.
>I have set blocksize to 0 in the calling prg, however the table was most likely not created with the blcoksize parameter set to 0, so your program above should sort that out. I think that this situation best explains the bloat that I am seeing
>Thanks for the reading material Tore, it explains the bloat, expecially with the blocksize parameter.
>The file is that bit too big and used too often and in too many places to have a running pack command at each use, I was thinking about running a nightly run that tries to pack.
>~M