Glad the problem is solved. I can understand the confusion about cursors, local views and tables (we'll ignore remote views until you're working with Oracle or SQL-Server ;-) Very briefly:

Tables are DBF files which may be linked to a database (DBC file) or may be free. They are physical files on your hard disk.

Views are always part of a database. Views contain fields from one or more tables and have specific properties which can be adjusted individually by field, allowing updates to the base tables etc. Views are based on SQL-Select commands, but are stored in the DBC.

Cursors are the result of writing a SQL-Select command in your code. Cursors are ALWAYS read-only when first run. If they come from a single table and if there are no calculated fields (and you haven't used the NOFILTER clause) then your cursor will in reality be a filtered version of the original table, not a separate TMP file.

USE dbf('MyOriginalCursor') AGAIN in 0 alias MyReadWriteCursor

command. However any cursor CAN be made read/write in this fashion.

For more information, read the HELP sections and try out a few simple samples.

HTH
Barbara


>Just what I needed. problem solved.
>Thank you
> You have me working with and manipulating cursors but I don't have a clear understanding of the relationship between a cursor,view and table.
> Why am I working with a cursor when I thought I was working with a table?
>Thank you
> George