I certainly don't think you can call it a bug. When you index on a field and there are duplicate values in that field you shouldn't make any assumptions about what order those will appear in. In FP DOS it did seem like everything would be in record order (or reverse record order) when there were duplicate values, but I always saw that as the way FoxPro happened to create the index rather than a feature. It sounds like you need an index on Acct+TransNo or a SELECT with both fields in the ORDER BY.

>In Foxpro Dos if an index is descending then the entire index is flipped upside down so that if the native order is
>ACCT TRANS#
>1 1
>2 5
>2 8
>3 10
>4 12
>
>a index on acct in descending order would result in EXAMPLE A
>4 12
>3 10
>2 8
>2 5
>1 1
>
>However in VFP the descending order is EXAMPLE B
>4 12
>3 10
>2 5
>2 8
>1 1
>If in VFP the descending index is opened ASCENDING it results in Exaple A's order.
>
>This is strange to me. Is this intentional or it is a bug in VFP?