Looks like a bug to me but it's not new to VFP9. I see the same in VFP8SP1. VFP doesn't generate an error if index order set to a field with integer data type even if there's no index with such tag name.

>Is this a bug? I can reproduce it at will.
>
>Table has 3 fields:
>---------------------
>k_seqno - autoinc intiger
>k_memo - intiger
>textln - 65 byte chr.
>
>1 index - on k_memo (I forgot to index on k_seqno.)
>
>If I open the table with:
>

use bsmemo order k_seqno

>I get no error message but show status shows that only the k_memo index exists and the Master Index is set to k_memo. I assume I should have gotten an error on the use command since the k_seqno index does not exist. Worse, the index is set to the wrong field. This just cost me a few hours of hair pulling.