Simon,
First, to split a table so some fields are in one table and some in another: Just copy Table1 to Table2. You now have 2 identical tables. Modi Stru each of them. Remove the memo fields from Table1 and the non-memo fields from table2. This will NOT affect the size of your FPT file, though.

Second, If your FPT is growing too fast, do a PACK MEMO on the table to get rid of any old memo data.

Third, to recover the memo data in the old table, restore BOTH the DBF and the FPT (and CDX if it's there) from the same backup set to another folder on your disk. When you're sure the data there is good, delete the memo field from your bad table, add it back again (save the table structure between moves). Set a relation to your restored, old table and copy the good memo data.

HTH
Barbara

>I hope someone can help me with this...
>
>I've been having problems with an fpt file.
>My client first noticed there was a problem when the size of the fpt just got bigger and bigger. then the whole system fell over. When we tried to use the dbf I got the error message memo field missing/invalid.
>
>I tried various applications to repair the fpt, but noe of them have worked.
>
>we tried copying an old version of the fpt from backup, and that enabled us to use the dbf. But we now need to be able to access the memo fields.
>
>Is there a way o completely rebuild the fpt file?
>
>I also want to split the dbf into two, and have all the memo fields in one and all the other data in another, for ease of packing, and to prevent something like this happening again. I tried to SELECT all the memo fields into another dbf, and the SELECT to about 24% and stopped. I tried to SCAN...Scatter Memvar memo, and got an out of disk space message. I also tried to select each field separatly and got 'no memory for file map'
>
>Does any one know what has happened, and what I can do about it?
>
>I will be very grateful for any suggestions
>
>Simon