>>>>Ye-gads,
>>>>Now we can no longer test the result of a query. RECCOUNT() will fail if the query is fully optimisable, because reccount() will return the number of records in the underlying table - unless you specify the NOFILTER clause which will slow it down.
>>>>So some time ago I stopped using RECCOUNT() and always used _TALLY. Now it's a dud there's nothing reliable left!
>>>>:-((
>>>
>>>"count to memvar" works
>>
>>That's right. Good one Albert. Could be slower though.
>>Thanks
>
>It is Rushmore optimized and respects deleted records and active filters. It is better that reccount() in these respects. The better answer can come at a cost, but Rushmore can help minimize it.

Also you could use:

select count(*) from tablename into array arrayname

This has the added benefit of not moving the record pointer.