I have encountered the error message "memofile.fpt is corrupt" in both 5.0 and 6.0. This seems to happen most frequently in a network environment when users attempt to update memo fields via .scx's (using optimistic row buffering).

But then when I go in and open the table from the command window and scroll through the memo fields, I can't find any problems. Issuing PACK MEMO doesn't hurt--but it doesn't seem to rectify the problem either.

This has been so frustrating that I asked one client whether they could live with character fields (of course this limits data entry to 254 chars).

Since this is a sporadic problem, I'm wondering if it might relate to network traffic?

I've not encountered this problem when updating memo fields via a .prg.