I bumped into a cbo behavior which might interest someone out there. For all I knew, I used cbos to select records from the underlying cursors and they worked fine except for non-unique columns. The cbos featured =, $ and ending-with searches in the Valid code. However, for non-unique columns, where multiple records which match search criteria are involved, I had problems with beginning-with searches (that are not EXACT-ly equal) that pumped in the correct value back into Combo.VALUE to force the underlying cursor's record pointer to move to the correct position.

I've done up a fom that demonstrates my point.