Steve,

Perhaps you are right. But, frankly, this one took a lot of steam out of me!

Jim B, for instance, argued with my statement that, for all intents and purposes (in this discussion) a table and a cursor are the same thing. He flatly states they are not! This is an argument I cannot win.
For instance, for all intents and purposes, in a discussion of currencies of the world, the US$ = the $Cdn = the Yen = the Franc. We all know they each have different VALUES, but I think we can all agree that they are the 'standard for currency' in their respective countries.

Francois' dilemma *WAS* corrected when he added NOFILTER to his SQL statement. That was enough for me to be able to say: point made!

Cheers,

Jim N

>PMFJIH, Jim, but in scanning the thread thus far, I don't see a definitive answer to Francois' question. The problem he's encountering is that SET TALK is OFF and he's checking _TALLY after creating the index. If SET TALK is OFF, INDEX or REINDEX will reset _TALLY to 0, as _TALLY is "turned off" by SET TALK OFF. SET TALK however does not have any effect on SELECT - it accurately returns the number of records in the result set. However this can bite you if you have a view that is already indexed, have TALK set OFF and issue a REQUERY(). The internal REINDEX that has to occur when the view cursor is repopulated resets _TALLY to 0. This is a case where you either *must* rely on RECCOUNT() to determine the result set, or create the indexes after checking _TALLY, but you have to be careful (as Jim Booth and others have pointed out) that you're getting the number you *think* you're getting.
>
>>Jim,
>>
>>*Hopefully*, this will be my last words on this subject. . .
>>
>>Francois was originally asking WHY the results were different. Several people had already told him the difference regarding RECCOUNT()/TALLY when I (finally) wrote.
>
>>>-Steve->>