I created a subclass of the wwMaint.prg and then put that behind an authentication. I then added various PACKing routines: Some pack all tables, others pack the "vulnerable to memo bloat" tables.
The problem is getting exclusive access to the tables. If you're running in COM mode, then WWWC has a way of stopping all instances except one. If you're running in File mode which is what I'm doing, I have to remote in and kill the extra instances and then run the pack. It's a pain.
I've considered moving the table to PostgreSQL and not telling the client. Tempted but I haven't gone through with it.
-Kevin
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Thursday, November 03, 2016 11:57 AM To: profox@leafe.com Subject: 2 GB memo bloat in DBF used in WebConnection site (was RE: Friday Poll (while dl'ing MS Flash Patch))
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?
tia, --Mike
[excessive quoting removed by server]