We currently have an fpt file that has reached 250 mb, When I need to add another memo field, I create a dbf with only the key and the memo field and relate it to the other database. This way each memo can grow up to 2 GB in size I do a pack memo once a week and save a copy of the pre-packed dbf and fpt just in case. Archiving old data or splitting memos among multiple databases is the way to fix the problem . I don't feel safe when a memo file goes over 1 GB. It's probably best to have some sort of warning built into your software that tells you when it's close to 2.GB so you can make adjustments. Once it goes over 2 GB, things get scrambled and may not open at all.
I have had minor corruption over the years, but nothing major that I couldn't fix from a backup. Of course, make sure you backup every night.
From: "mbsoftwaresolutions@mbsoftwaresolutions.com" mbsoftwaresolutions@mbsoftwaresolutions.com To: ProFox Email List profox@leafe.com Sent: Thursday, November 3, 2016 11:14 PM Subject: Re: 2 GB memo bloat in DBF used in WebConnection site (was RE: Friday Poll (while dl'ing MS Flash Patch))
On 2016-11-03 19:25, Richard Quilhot wrote:
Divide the data into smaller DBF's then add code the select the correct small table that needs updating.
Not an option at this point. Besides...this table has only ONE memo field.
[excessive quoting removed by server]