Larry,

First, I ASSuME that when you say "large data file sets" you mean large .DBF/.CDX tables.

1) What is/are the larger and more heavily used tables and what exact index TAGs are defined in each?

2) Do your WHERE/FOR etc. clauses have expressions coded that match the TAG declarations exactly, as required for Rushmore to operate?

3) Are the multi-users all using some 'proper' network/file-server OS, as opposed to WinXX peer-to-peer?

4) Does the application use lots of SQLs or LOCATEs or SCANs. If so, which?

5) Are you deliberately locking records or are you leaving tht to VFP to handle?

6) What type of buffering/locking is in use in the application?

250K+ records in not at all "large" and VFP should be able to process instantaneously in "regular" style processing.


good luck
>Hi -
>We have an app. that generaly manages large data file sets. The app. is a mulit-user app. We have found when the data files get quite large (250K records + in each file set) and as more users log into the system the app. pefermance slows down dramatically. Can someone please help point us in the right direction.
>
>We have :
>Set multilocks on
>Sys(3050,1,10000000)
>Sys(3050,2,6000000)
>Set REPROCESS TO AUTOMATIC
>Set DELETE ON
>Set OPTIMIZE ON
>Set RESOURCE OFF
>
>
>We have also added to the config.fpw
>tmpfiles=c:\work
>editwork=c:\work
>sortwork=c:\work
>progwork=c:\work
>set refresh to 0,20
>BITMAP=OFF
>
>
>PLease can someone assist us.
>
>Thanks in advance.
>
>Larry
>instructed users if their workstation OS config.sys has FILES to increase to 255 (FILES=255) and if they have BUFFERS to increase to 40 (BUFFERS=40)