Divide the data into smaller DBF's then add code the select the correct small table that needs updating.
Rick Q quilhotr@gmail.com
On Thu, Nov 3, 2016 at 2:24 PM, Gene Wirchenko genew@telus.net wrote:
At 08:56 2016-11-03, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2016-10-28 10:24, Kevin J Cully wrote: X DBFs - I have a client that insisted I use DBFs for his desktop and Web-Connection site. It's run almost flawlessly since 2008 with the exception of the 'memo field bloat' issue. That's caught me a couple of times over the years hitting the 2G limit per file.
I'm handling one of Jeff Johnson's (RIP) clients and having this issue.
I was about to create a simple utility for the end-user to grab the table and pack it, but curious if you've got a better idea?
I have a routine that packs and reindexes all of the tables. I havenot needed anything more involved.
I do see some memo bloat. I have a table that stores configurationdata. When packed, the .fpt is 1280 bytes. I see from the latest sent to me that it is up to 5,205,248 bytes. That is bigger than the source code.
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]