>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.

if this is indeed the case you can reverse the use of deleted and use
the delete flag to mark active records (because !deleted() is not optimizable and deleted() is )
this way when u do SELECT .... WHERE DELETED() ...
it will be optimizable (if you have an index on deleted)

Arnon