I've had a nasty little cursor unknown exception keep popping up from time
to time.
Some people have offered that it must be (or most likely is) associated with
a missing KeyLinks property in a query. I was determined that it wasn't
since all my searches on my component properties brought back no luck in
this area.
I have now finally found that it was associated with the queries used in
LookupCombos. Specifically the queries which display only field contents and
have a keylinks property in the form FIELDFROMTABLE1=FIELDFROMTABLE2.
I now know that these queries cannot have the KeyLinksAutoDefine property
checked. If you uncheck it, the Unknown Cursor exception finally gets put to
bed...
Hope this helps anyone else with the same problem.
Alan


[Non-text portions of this message have been removed]