Fabio,

>>>VFP handles memo fields differently depending on if the table is exclusive or not.

>>....In exclusive if the memo will fit within the current space it'll reuse the block.

>not true

The code I posted shows it to be true for tables which is what Jim was discussing in this subthread. I was providing example code to illustrate the difference between exclusive and shared access memo handling.

I'm pretty sure (read that as not very interested in running it right now to verify) that any code you posted in this thread is misbehaving from a VFP standpoint because of your use of SET COMPATIBLE ON.

My code opens and closes the table so that the O/S gets a chance to flush the file to disk to get a reliable size for the file via adir(). You can do a hexdump of the dbf to prove to yourself that the same memo offset value is used in each of the cases where the memo size decreases and therefore by definition fits within the currently allocated block. When blocksize = 5 and exclusive mode the only time the fpt increases in size is when the memo is first allocated, after that the size is static because all of the operations on the memo do not make it exceed the size of it's currently allocated block.

If you can show an error in my code please do.