Thanx for the quick reply, but I've been using VFP7 since it came out so I don't think that is the case. Also I have tried reindexing with VFP8(and service pack) with the same result.

>Hi Paul,
>
>There's a bug in VFP7 that significantly increases the size of indexes created in it compare to VFP6. It has been fixed in VFP8.
>
>>Not sure quite how to explain this, but here goes. First of all, I am using VFP 7.0 with all of the service packs installed on Win2K Pro. I deal with a lot of large tables - 800MB to 1.7GB. They all have the exact same columns and indexes, just different data, oh and nulls are not allowed. It's a data warehouse, so once the tables are loaded they are pretty much static. The code I've been running has been running really fast, like it's supposed to. Recently, within the last month, I noticed that my processes that report on these tables have slowed down considerably on the last months batch of data, but run just as fast as they had been on months prior. In comparing the size of the indexes relative to the tables, I noticed the indexes have doubled in size, while the size of the data is about the same. What would cause this??? I noticed that somehow the collation sequence had gotten changed from machine to general, so I deleted the indexes on last months data and set the
>>collation sequence back to machine and rebuilt the indexes. The indexes did decrease in size, but the process still slows down when it hits last months tables. I thought, ok, let's delete the indexes from the April data and rebuild them just to see what happens. Well, now Aprils data is just as slow as May data! What do I need to do to get my speed back?!? Is there some other setting that I am missing?