A client of mine has issues with slow response times. So, I was trying to understand this a bit more clearly than I had previously understood it. I've been able to help some clients with improving response times by rebuilding their index files from scratch, doing a delete tag all, etc., but, of course, I recorded the index expressions and tag names beforehand. I've also archived clients' data to archival tables so that the table files are reduced in file size, which seemes to help also.

>>Isn't it true that when a workstation looks at data in a FoxPro table on a VFP form, that the entire table comes down to the workstation physically, perhaps as a temp file that is recognized as the table? And, isn't it true that this causes the LAN's bandwidth to be high if the tables are large?

>Not necessarily. If I remember correctly most of what comes down the line is index data that VFP uses to determine where real data is (depending on the operation).

>It is true that this can use a lot of bandwidth on large tables, large result sets, or with complex queries.

>SQL Server and other server based databases can be much more efficient (unless they are pulling large result sets - then they are about equal).