When you run the SELECT it is read-only. However you add one more line of code:

Select ..... into cursor MyTempCursor

USE dbf('MyTempCursor') again in 0 alias MyReadWriteCursor

The USE again makes a read-write copy. Note how the dbf() function gets around not knowing what the cursor is really named. This ONLY works if you have a 'real' cursor, so use the NOFILTER clause if there is a chance your cursor will be a filtered recordset. If you don't have a calculated field and if your cursor comes from a single table, you will have to use NOFILTER.

HTH
Barbara

>I thought a cursor created with a SQL select was read-only..is there a way to make it read-write w/o selecting to a table?
>
>Chris