>I had a client call me with a "FPT file is either missing or invalid" error during the reindex process. When I received the backup I could open the file to read the memo fields, append records, and delete records without the error. The error only occurs when issuing a PACK. I fixed the problem by creating a cursor to hold the data, zapping the original table, and then appending the data back into the table.
>
>I've never had this happen before. Any ideas of what caused this?

FPT can get corrupted in a variety of ways. The main one I have seen is the user is in the middle of an update and their computer loses power (or hangs). When they get power restored and fire up the application, the FPT is corrupted. I have also seen the recorvery technique that you used work. But in my experience using the same method. The data was not totally recovered and some memo fields were missing that were present before. So I would recommend that you check the data out as much as you can before you send it back and tell them it is complete.

My two cents.