>Dragan,
>
>I think you should just save the _tally result after the command that creates the result set before you index the result.
>

Not applicable in this case. The routine I use to create the cursor just copies the structure of the underlying table into a cursor, with an additional rcn field to keep the original record number, does a seek and then copies records one by one via scatter/gather. I use it when I expect a very small recordset from a large table. In this case it's just one customer's unresolved records (i.e. unpaid invoices). Works faster than SQL for cases like this.

Of course, in a larger scale, it would be better to use a parametrized view and simply requery, which it will be once I get down to it. I was just bothered with the (unnecessarily) changed behavior of _tally - one more thing to watch out fore while migrating the code, and kind of a waste of time.