Fix fpt file without foxfix?

[Olaf Doschke]

Today I had a severe case of memo file bloating. It seems this happened more often and regularly, already.

The table involved is used for checked out data tranferred from a client to a notebook and later transferred back. The data on the notebook grows and shrinks, but in this case grew to 2GB minus a few bytes. Nevertheless the fpt file is already corrupt, so I can't PACK MEMO or PACK, even when SET TABLEVALIDATE TO 0, the table doesn't open.

Today problem is solved by copying over the full table from the server to the notebook, it doesn't need the full data of that table, but it also doesn't hurt. In the future I'll add a PACK MEMO before or after each data transfer. So problem is kind of solved already.

Nevertheless is there a comparable easy fix like the one to fix a wrong reccount in the dbf header, that could be applied to bloated FPT files?

Bye, Olaf.

 

[Olaf Doschke]

A related question of course is, would foxfix be able to fix such fpt files which grew over the 2GB border by the memo bloating effect and then didn't save fully or correctly and thereby got corrupt?

The file is not larger than 2GB, but very close, so while VFP failed to write the last change, obviously, it also didn't reverted the fpt file to the last working state. I assume that is because the involved table has many memos fields.

Bye, Olaf.