>>Ah, this all makes sense now. If you SELECT into a cursor, the cursor is not editable. Still strikes me as odd behaviour but I guess that's just the way it is.
>
>Anne,
>
>You can easily make the cursor editable. Here's the code...
>

>FUNCTION EDITCURS( tcCursorAlias )
>*  OVERVIEW:   This routine converts a readonly cursor into a writable

[CODE DELETED FOR BREVITY]

>RETURN
>
>ENDFUNC>
>The problem with using a writable cursor as a grid source, compared to say a view, is that you somehow have to move the changes in the cursor back to the source table(s).  For that reason, most developers use either a table or view as the data source of a grid.
>

Thanks James - it's an interesting approach.  I actually wound up simply sending the results of the query to a table instead of a cursor.  A little more work for what I was doing, but it works fine (surprisingly fast too!).  

-Arne

arne@synercom-edi.com "There are no absolutes but this one."
President, synercom/edi - Event Ticketing Solutions