> The short answer is that you need to rethink the approach how do you work with those tables: indexing, optimization, reducing the number of records by using views, etc... Details will depend on what actually is implementing by code and how.
>
> > I'm sorry to bother you guys again, but I have a problem that I need to fix, and I don't know where to start. I wrote a database program using visual foxpro 6.0 that runs great at about 98 percent of our clients establishments. However, we have one client with a significant amount of data including some tables with close to a million records. The performance of this clients program is drastically worse than our other clients. Is there anything that I can try that will increase the speed of the program. If it helps our client is using a NT 4.0 server with 15 windows 98 workstations. I really appreciate any help that you guys can offer.
> >
> > Thanks,
> > Chris Counts


Hi,
Would help the team if you were specific in what areas of your application you have the slow speed....
In large databases some general guideline are.
... never use filter
... use SQL to extract views if possilby
... if you are involved with updating let me know... I have some large table tricks that you may be able to use.

Unfortunately, system design for extremely large tables is quite a but different from medium sized applications,
and some extensive re-code may be in order.

Pete from the Great White North. (Only in Canada, ay.) Over and Out ...