>Hi Ssergey,
>just to be curious, what is a new index changing RECCOUNT()? Until now I think RECCOUNT gives me all Records no matter if they are filtered or deleted? Which was the wrong result (after INDEX ON?)
>
>Or is this only for a pseudo cursor from SELECT SQL? (I learned this problem on my early foxpro days do I never thought about it as a cursor it's more like a filtered alias after USE .. AGAIN ALIAS ..)
>
The program was checking the # of records using RECCOUNT() on a cursor. It worked because SQL SELECT that creates this cursor wasn't Rushmore optimizable. The index added to the table made that query optimizable and consequently RECCOUNT() returned the # of records in the table not in the cursor.