Very true, Jerry.
If you don't want the UNION to remove duplicates, use UNION ALL and it will
be faster. If you do want to remove duplicates, then it will take a while.
This is as you have stated. However, any other method of producing the list
will have that penalty when it is needed, so there's not much of an argument
there.
Beyond what you said, the combo box has an upper limit of 65K rows that can
be very troublesome. I have a subform design that can substitute, and even
pops up. It only retrieves as many rows at one time as are displayed, and
has no upper limit. One key to this is using a vertical scroll bar control,
that changes the subform's RecordSource to be the TOP N needed to fill the
list needed at any moment. The OnChange event allows the search to automate
the change of RecordSource as a user types, so all the behavior of the combo
box is emulated without any of the performance or other limtations.
That was several days labor to create. Some day I may need to produce a
wizzard that does this automatically and publish the whole thing. Sigh.
I like your "Pick two." motto. I am a former bicycle repairman and racer
(college days). It's widely applicable.
Tom Ellison