Re: combos in large app
- From: "Rick Brandt" <rickbrandt2@xxxxxxxxxxx>
- Date: Thu, 22 Nov 2007 03:51:56 GMT
miss031 wrote:
I generally filter the RowSource for Combos if the list will have
more than a few thousand rows. However; I do that to reduce LAN
traffic and resources on my database server, not because it will
make the list faster for the user. In many cases a really long
list in a ComboBox with AutoExpand enabled will still be plenty
fast.
Thank you. That's exactly what I mean - not actual speed for the
user, but drain on resources. Please tell me how you would recommend
I proceed.
What I typically do is use the GotFocus event to prompt the user for starting
characters and then set the RowSource of the Combo to a SQL statement using
those characters as filter criteria. Even just 2 or 3 characters will usually
reduce the list size to a manageable number of rows.
On one or two occasions I got fancier and laid a TextBox on top of the Combo and
made it look more seamless, but I generally find that to be more trouble than
it's worth. Particularly if you want a seamless response when the user
backspaces or deletes.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
.
- References:
- Re: combos in large app
- From: Rick Brandt
- Re: combos in large app
- Prev by Date: Re: DMax sorting incorrectly
- Next by Date: Re: DMax sorting incorrectly
- Previous by thread: Re: combos in large app
- Next by thread: LINUX RULEZZ
- Index(es):
Relevant Pages
|