You are not even beginning to scratch the limit of vfp - your problem is not vfp, not tables, etc. It is 1) something that is incorrectly developed, or 2) a problem with the server hardware.

1)
Incorrect Indexing or lack thereof
Unnecessary information being sent across the wire (only data needed to produce the pages needs to be sent to the client)
Etc

2)
Bad installation
Lack of sufficient hardware to handle the load (RAM, Processor, etc)
Etc


SQL 2000 will not help with any of this - if you still don't have it tuned correctly. And it will probably hurt instead.

Detail a bit more about the setup of the system...
Hardware
Software
What application is used for the web component?
How is the data accessed?



>Hi All:
> One of my client have a web site with a backend data in vfp 6.0. There are total of 80 tables. The tables are free tables. The average number of rows in the tables is 80,000. This web site runs real slow, often taking minute or two to refresh a page. They were told that they need to redesign their whole data files and the web site. The client do not want to do this, as money is the issue. I was think of converting vfp tables into sql 2000. Would this solve the issue of performance?
>Any ideas of suggestions are greatly appricated.
>Thanks
>MA