>This might be another 'stupid' question of mine, but why would you index
>on DELETED()? I tried it and it resulted in listing all deleted records
>after non-deleted. What do we accomplish by this besides this obvious
>effect?

This was the way to go to be fully optimizable until Visual FoxPro 3.0. Of course, this was applicable if we were working with SET DELETE ON.

Its use is not to have a visual tag but rather to be optimizable, at least was.

If you always work with SET DELETE OFF than this was not applicable. And, if you are working with SET DELETE OFF than what is your mecanism to avoid dealing with deleted records?