I agree with you. The history of this goes back to at least 97 and it has not become a priority yet. One could stop using SET ORDER TO 0 and use SET ORDER TO TAG MYATAG (based on INDEX ON "A" TAG MYATAG) instead. Then Fabio's code would always work to optimize GO BOTTOM.

>Fabio,
>
>I guess you´re right. This indeed would make it simpler. However I´m not sure on how many VFP developers are waiting for this feature and if the VFPT should implement this.
>
>IOW, I don´t think many developers would regard your problem with the non-optimizable GO BOTTOM as such a big problem that it should be addressed in the next version at the cost of some other equally time consuming feature request.
>
>By no means I´m saying that you´re wrong. In fact you do have a valid point up here. The only question is if it is important enough to make it for VFP.Next
>
>Walter,
>
>
>>
>>I agree that might be usefull in some cases.
>>
>>
>>With this, the TAGNO zero is the natural RECNO() order,
>>and your code he becomes very simpler for every situation:
>>

>>* optimized GO BOTTOM
>>IF DESCENDING()
>>   SET ORDER TO TAGNO() ASC
>>   LOCATE
>>   SET ORDER TO TAGNO() DESC
>>ELSE
>>   SET ORDER TO TAGNO() DESC
>>   LOCATE
>>   SET ORDER TO TAGNO() ASC
>>ENDIF
>>