>>>>What about other software and/or processes running in the Task List?
>>>
>>>One of the ME systems that is having the problem has this list on Boot up, which is where I tested:
>>>Explorer, HotSync, NAVAPW32, SysTray, and the VFP 6 application to run the test.
>>
>>Do all the machines have VFP6 SP5 runtime installed?
>Using Wise Install, I would expect them to.
>However, one of the systems I am doing this within VFP 7 from a prg file.
>The VFP6R.DLL is 6.0.8961.0, which is SP 5, is on each machine.

Is there any distinction between machines running on NTFS vs. FAT/FAT32 partitions?

Beyond that, I don't know what else to offer. Maybe you've found a bug < g >

Another question just crossed my mind. When you SET BLOCKSIZE TO 512, each memo will take at least that many bytes in the memo file. However, I don't know what the behaviour is when what you're putting in is not exactly 512 bytes. I'm not sure you can rely on VFP to overwrite the unused part of a block with something like CHR(0), it may just leave the remaining data on disk alone entirely (i.e. whatever was there before is still there). As long as the offset and length of the memo are set correctly in the .DBF and memo no-one should care what is in the unused portion of a given block. Clearly VFP doesn't care if it's not displaying any "corruption".

Are you seeing corruption in the part of block(s) that you know should contain certain known data, or are you just seeing "corruption" after the data you've written?