I can only say that some of the methods should be reviewed and time testing should be done with a variety of number of users accessing the table at the same time. In other words, sometimes a method that proves to be the fastest when you are accessing the table as the single user will not be the fastest method when there are many users.

I would also check each operation to see how fast (slow?) it is when done from a remote machine and how it does from the application run on the file server. If the file server can do some operations a LOT faster, I would explore the use of DCOM to get these operations done on the file server.

I guess you might want to look at SQL Server too if this continues to be a problem.

Joe


>A client of mine has a problem with very slow table access. This is their situation:-
>
>Windows NT4
>Citrix/WinFrame Terminal Server
>VFP5
>One of their tables contains 8+ million rows.
>Table size is 1.6Gb
>About 100 users.
>
>The table in question is being hit quite hard and some extremely slow responses have been measured. One operation is selecting data from the table, others are inserting into the table. Those that are inserting are *hanging* and task manager shows *not responding*. I've explained to the user that the process is too busy to respond to task manager.
>
>Another operation that updates the table has taken all day to update about 1,000 rows.
>
>Does anybody have any experience with this kind of slow-down? Any solutions?