>Is this true only for the deleted index? I use set deleted on so deleted records are not picked up until the dbf can be exclusively used and packed. Reworking this is a major pain. I don't use a deleted index very much. SQL's don't pick up deleted records from tables with set deleted on. If a table has deleted records, does performance drop significantly?

Yes, this is a major pain and reengineering has to be done. The problem is dealing with high volume tables. I've built 5 applications in Visual FoxPro until now and didn't have any problem because I didn't have more than 10000 records. Now, with the latest application, I have 100000+ records and this is not acceptable. The system dropped completely.

If you would have follow George Goley session at DevCon, he mentioned that, no use of SET DELETE ON anymore. I couldn't believe it so I tried this with the latest application and I was FRUSTRATED of this new infrastructure in Visual FoxPro.