If someone else is in the program with the tables open, reports will be slow, and the client interface will be slow. It's a network share thing. Some of our customers see this when their data gets above 3000 records. I deal with legacy code that came from the original clipper code base. You know the kind that does a SCAN ... ENDSCAN to build the report data.
YMMV, Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of mbsoftwaresolutions@mbsoftwaresolutions.com Sent: Thursday, August 23, 2018 5:19 PM To: profoxtech@leafe.com Subject: Re: Lianja anyone?
On 2018-08-22 12:27, Alan Bourke wrote:
On Wed, 22 Aug 2018, at 3:51 PM, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
On 2018-08-17 10:08, Dave Crozier wrote:
They've got 500MB of data in some centers with 20+ years of data
Not *that* big in Fox terms ...
running some reports takes FOREVER on the client machines at their learning centers
Are they on the same LAN as the server with the DBFs?
I agree...not huge for VFP but for reasons I can't explain, it's slow. Of course the tech folks at Corporate think it's pulling the entire dbf file etc over the LAN (and maybe they've done analysis to support that with SysInternals...not sure), but I've seen it to be slow. Many lines of legacy code that weren't written for full optimizations, so it is what it is.
Yes, I believe the same LAN. Workstations connecting to the inhouse Corporate server box...which then communicates with the MotherShip and sends all their data back there too. I believe the servers are underpowered and not configured correctly but of course that's off-limits to anybody but The Man at Corporate.