*-- one thought
Are you using rowsourcetype = 3 - SQL Statement for your listbox on 1st page?
If so, possibly there is some type of conflict with the name of the cursor created there?
- have seen this cause unexpected results before

*-- another thing you could try
use a free table dbf in the temp folder on the local workstation instead of a cursor for your grid, then it might not complain about cursor rules?



>>>And this is funny... I've switched to a CREATEd cursor, and it works now, except that the grid seems blank until I open another window. Seems to need an extra refresh - yep, that works.
>>>
>>>So it was probably that "select * ... where .f. ... readwrite" wasn't really respecting the implied NOFILTER, and the cursor behaved pretty much like a view. Very interesting.
>>
>>Now I switched back to
>>
>>select * ... where .f. ... readwrite NOFILTER
>>
>>and it works... which means not all cursors are created equal.
>
>No it doesn't. It goes through zap/insert fine, but I got other things happening to this cursor, i.e. other records updated programmatically while the grid has focus (actually it's a commandbutton that gets the focus, but it doesn't seem to matter). And it's the same with both the created and select-nofilter cursor.
>
>I somehow get the feeling I'm back at square one.