>>*not only does it change the record in temp2 but it changes the record in out
>>
>>what if you don't want the changes to reflect in the out table, you only want to modify the cursor. do you have to use the create cursor statement.
>
>That means not only that "use again" on a filtered cursor gives you a read/write cursor which is a filter on the original table, but that it actually behaves as an updateable view... which would be a nice shortcut, if we could rely on it. Since Fox decides when it will be a filtered cursor (unless we put NoFilter in select, we never know if it will be filtered or not), we can't.

OK, I've done some testing on this. The reason it changes the record in the original table is that on a filtered cursor dbf() returns the original table's filename. Your Use Again does not use your cursor, but it uses the table. So if you want to use this great tipODday, include NoFilter in your initial SQL Select, else you may end up messing the original table.