>>>
>>>You should look into why memo is growing so fast. Most likely it's result of to many updates on memo fields. Every time a memo field is updated, it's copied entirely to the end of FTP file (unless table is open exclusively).
>>
>>
>>I'm aware of what is causing the issue, and I have plans to address that. There's a nightly automated job that updates this table and makes thousands of updates to this memo field. I intended to remove the memo and replace it with a character field of reasonable size, since it isn't critical that the entire contents of the source field be available all the time.
>
>A better strategy would be to collect all the updates in memory and write them to the memo once. Then you can keep your history without memo bloat.
>
>Tamar

I may not have stated what's happening very clearly. The table has about 400,000 records in it. The update happens once per day to each record, if that field has changed in the source table.