>>Some time ago there was a thread concerning speed in VFP5.0 with SET DELETED ON. How are you addressing this issue in the UT engine?
>
>We found the problem. It was not related to SET DELETE ON.

I thought there was a thread indicating that the underlying VFP data engine had some changes in it that resulted in SQL queries running slower than in earlier versions when SET DELETED was ON and that queries of this type could not be optimized even with the existence of an index on DELETED(). I also remember George Goley stressing at the last DevCon not to run queries with SET DELETED ON due to the performance hit. Is this incorrect or have I missed something?

Thanks,
Bill