In fact I have, now, 3 places where I can get unknown cursor exceptions.
1. see previous post where KeyLinksAutoDefine is True when it should be
False for Lookup Combos.
2. Where I need to have an action which deletes a record currently in view
via another connection and transaction. When I try to refresh the current
view, I understandably get unknown cursor since the grid is trying to fetch
a row which now no longer exists. Easy fixed by forcing a Close and Open on
the Query.
and

3. where I need some assistance...
I have a LookupCombo which has two fields which get assigned to the query it
is linked to. One field is an integer, the other is a Float.
Now when I refresh this query I ocasionally get Unknown Cursor.
As I understand it, the Keylinks definition is being used to assign a value
from the source into the link query, and it is also being used to locate the
record in the lookup.

Question: Is there any way I can make this arrangement use only one of the
keylinks to do the lookup, but use both to do the assignment?
Thanks
Alan