Hi Moises,

>For example in the way their data are saved to the table

No, not at all...

if you specify a view or a table in the data environment as a cursor, you can simply use the REPLACE command to change fields. With buffering you would need TABLEUPDATE(), as well.

For cursors that are the result of a SELECT statement, you have to write a SCAN or DO WHILE loop that goes through all modified records.You have to write different code for updates, delete, insert and recall. For update, the code would look them up in the original table and transfers modified field. This could be an UPDATE statement that you generate, or a combination of SEEK and GATHER. Inserts can be implemented with an INSERT statement, or by using APPEND plus GATHER. Delete operations would need to be implemented using the DELETE command. Since you are operating on a different table, you also might have to take care of conflict resolution.

A cursor in the data environment is the equivalent of the USE command. It has nothing to do with the SELECT-SQL command.