Oops . . . my bad . . . I had accidentally used that cursor name in the INTO CURSOR clause of a SQL SELECT statement, which blew away the cursor I had specifically created via CREATE CURSOR and the new version was indeed read-only (since the SQL SELECT statement needed no READWRITE clause). Ah, the disadvantages of cut and paste . . .

>I'm running into a strange situation where I use CREATE CURSOR and for some reason the cursor is read-only. This is under Terminal Services and I've recently run into some oddities running in that environment. To make this even stranger, I was testing a form and it was working fine and then it stopped working (meaning that the cursor I created and was adding records to and zapping began giving me the read-only error). I had set up the cursor to be created when the form loads and haven't changed that code, yet now it just suddenly gives this error. Anyone seen this before?
>
>Russell Campbell