>>I have a very large table containing approximately 5 million entries.
>>It has always been stated that it is a good practice to create an
>>index tag on DELETED(). However, when browsing a VFP 5.0
>>table with this number of records the time to see the results
>>is Very SLLLLOOOOOWWW.
>>
>>SQL queries also seem slower unless you SET DELETED OFF.
>>If that global setting needs to be turned off to get performance
>>what is the point.
>>
>>I have heard from one of if not the best FoxPro guru's that
>>what is taking place is that the bitmap of the deleted tag will
>>be copied to the users local PC. This truly appears to be the
>>case when viewing the number of bytes being transfered
>>across the network.
>>
>>Anyone else out there dealing with large tables with a deleted
>>tag? Not sure the best approach. I know that the SYS(3054,11)
>>function will not return a FULL optimization with an index tag.
>>
>>Your thoughts on this matter will be appreciated...
>
>DELETED() tag is necessary for most of people, and highly recommended for others :). With this tag you should get full optimization, if not then something else is wrong. Surely, SET DELETED OFF is radical cure to speed up queries, but in most cases you don't want to retrieve deleted records. Last year (somewhere in Aug or Sep) we had extensive discussion of this topic on UT. You coud search for that thread.

Edward, thanks for your reply. Unfortunately, I do not at this time have access to
the archieves. Any possibility that you could do a quick search and perhaps
send one or several responses from the UT discussion back in Aug or Sep?
Why is it that I only have a problem with DELETED() tags and not the other
index tags?