> >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.
>
> This really wouldn't happen, since KeyLinksAutodefine doesn't override
> user-entered KeyLinks - including those that you enter for lookup
> keys. It
> won't do any harm to set it false but it's not an issue when Lookup
> Keylinks are used properly (so, see my comments on 3, below)
>

I'll comment here separately...

I've reproduced this over and over now.. I'm sure it makes a difference - at
least to what my understanding now is to what "properly" means.
My lookup query has the key equality statement which matches the source
query field to the lookup query field. If KeyLinksAutoDefine is true and
your cursor is selecting the drop down box when you "Transaction.Refresh"
you get an "Unknown cursor" exception. If your cursor is not resting i.e. if
the drop down box is not currently focused, the exception is not raised. If
you set KeylinksAutoDefine to False, then it doesn't raise an exception
whether you have focus or not on the dropdown.

Alan