Hi,
Check the char field occasionaly, you will see the control characters.

FWIW the exact cause of the corruption at either end of the file is unknown, possibly Network, software or hardware errors, all this method dose is keep the system running without grinding to a halt.

The cache problem is a totally different problem with other resolutions i.e. disable write caching & oplocking, which I will list below.

XP workstation reg Hacks

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters]
"UseLockReadUnlock"=dword:00000000
"UtilizeNtCaching"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MRxSmb\Parameters]
"OplocksDisabled"=dword:00000001

Win2003 Server reg Hacks

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters]
"autodisconnect"=dword:ffffffff
"CachedOpenLimit"=dword:00000000
"EnableOplocks"=dword:00000000
"enablesecuritysignature"=dword:00000000
"requiresecuritysignature"=dword:00000000
"SizReqBuf"=dword:0000ffff

>>>There are references here on UT regarding this, mind you some time ago. I >> will see what I can dig up.
>
>>>Look at Message # 941950
>
>
>Neil,
>
>I though these where more to do with cache problems and VFP updating the table header before records are saved back to disk. These I have seen before and continue to see & repair.
>
>My worry over this one is that there is only one record in the table and none are every added or removed, We have over 80 installs of this product starting roughlt 8 years ago and i have never seen this corruption.
>
>Have taken you advice though and added the character field.
>
>Many Thanks
>
>
>Gary.