Neil,

The only thing that comes to mind, if you are not already doing so, is to try commands like UNLOCK or FLUSH at strategic points in the code. This presumes that the related memo field reported as troublesome is being written during the process, and not just read.

If it is reading that seems to trigger it, then you might try a strategically placed GO RECNO("aliasInTrouble") or play with the SET REFRESH command to see if they help.

Finally, because I know someone will come along sooner or later and say it, do remember that FPD is a very old "base" by now (I don't think it is even supported officially any more by MS). While that really shouldn't matter in the general case, hardware and OS's since that time have made amazing strides and applications have become more intertwined with the OSes they run under.
Since PFD/FPW are basically self-contained DOS-based applications they do not have the OS 'integrated' into them like later version of VFP and other software does.
All this to say that it is not particularly reasonable to expect, TODAY, that a DOS era software product will operate cleanly and correctly on modern hardware under modern OSes.
KEEPING the FPD application running on its old hardware may not be the optimum solution, but it definitely should be considered as an alternative.

good luck



>Hi Jim,
>
>Thank you for jumpimg in. The data is OK. Can you think of any other fix that won't require my users to reconfigure their box each morning?
>
>Neil
>
>>Neil,
>>
>>You say "...go back in and all is fixed.".
>>Does the user verify that any recently worked-on records do indeed show up correctly and that all of the memo fields in those records have full content expected?
>>
>>By the way, Sergey suggested disabling the write cacheing on the HD, which is something that may certainly be related and is possible (at least in my configuration of Win2K). BUT it does NOT "stick" between re-boots, so do remember to do it every time if you do try that.
>>
>>good luck
>>
>>
>>>Hi Sergey,
>>>
>>>Thanx for helping. The user upgraded from win 98 to win 2000 prof.
>>>Any thoughts?
>>>Neil
>>>
>>>
>>>>>Hi,
>>>>>
>>>>>One of my users, still using a foxpro 2.6 app upgraded a work station from a pentium 2 333 meghtz to a 1.4 gig pentium 4. Every once in a while the user gets an error message that a databases memo file is in trouble. All that we do is exit the program and go back in and all is fixed.
>>>>>
>>>>>Any thoughts?
>>>>>
>>>>>Neil
>>>>
>>>>
>>>>Did he upgraded OS also?