SNIP

Hi Ed,

While I agree that a second field which is not a part of an index can occur in any order, there may still be something unusual here.

Are we not told that say, for an index created in the (default) ascending order, a SET ORDER...DESCENDING will simply cause the index to be read in the reverse order?
That's how I read things, and if this is the case then how do the records become presented differently (or I guess I should say the same)?

Cheers,

Jim N

>
>It's not a bug; if the second field is not a part of the index expression, VFP doesn't consider it as a part of the index sequence, so the order can be completely random. If you need a key to order on both fields, then create an index that includes both fields in the index expression. All that happened with FPDOS is that you got lucky with the order that records were encountered or added to the file when creating or maintaining the tag; insert the records in a different order into the table, order have the records occur in a different physical order in the table, and the results you got wouldn't be reliably duplicated.