>Are there any speed advantages to using cursors? They seem to have an associated file on disk, so I get the idea that a cursor is just a table the VFP will erase on closing.
>
>Is this right? Should I write more complex code to move tables into cursors for high speed read/write operations, or just go ahead and use the tables?
>
>Thanks

Cursor is temporary table, so if you need in some data storage on fly, then cursor is natural choice, i.e. it's mostly design-driven and not necessarily speed-driven choice. In some situations cursors are much faster than tables, but if you need in read-write cursor then it will be created on disk with the same speed as if you would create a table. However, your code will be simpler because you don't need to care about erasing temporary files.