I would change index expression to use left(route,1)="B" instead or route="B"

>Everything is stored as character fields I presume?
>
>If so I would check the data, take into account paddding of fields, and case of characters.
>
>
>>Sorry about that... it's just a mistake in my example. I tried to used Route in the example to try to be more clear the actual data is "1CART"
>>
>>Any clues??
>>
>>Thanks,
>>
>>James
>>>Your index expression says
>>>Stream = "1Route"
>>>Your data has Stream = "1CART"
>>>
>>>Is this just a mistake in your message??
>>>If not, I believe that the Stream != "1Route" would not get indexed...
>>>Also remember it is case sensitive.
>>>
>>>
>>>>Hi All,
>>>>
>>>>I am trying to index a data view. The problem is... it doesn't exactly get indexed... huh?? Yup, it indexes a portion then starts again for another portion. Here's an approximate example:
>>>>
>>>>

>>>>Index on Stream+Zip+Route+Sequence+IIf(Route = "B", Zip4, DelivPt) Ascending Tag SeqA For Stream = "1Route" and SeqOrder = "A"
>>>>

>>>>
>>>>This return something like the following (note the "zip4"):
>>>>
>>>>
>>>>

>>>>Stream  Zip     Zip4   Route   Sequence
>>>>------  -----   ----   -----   --------
>>>>1CART   96800   0010   B001    0001
>>>>1CART   96800   0017   B001    0001
>>>>1CART   96800   0025   B001    0001
>>>>1CART   96800   0140   B001    0001
>>>>1CART   96800   0015   B001    0001
>>>>1CART   96800   0033   B001    0001
>>>>1CART   96800   0087   B001    0001
>>>>1CART   96800   0118   B001    0001
>>>>
>>>>

>>>>
>>>>Is this a FoxPro 7 issue or is this a Indexing views issue... I'm not sure but any information or advice would be much appreciated.
>>>>
>>>>BTW, the view is not set to write the data back to the original table.
>>>>
>>>>Aloha,
>>>>
>>>>James