Using unbound combobox

  • Thread starter Thread starter Roy Goldhammer
  • Start date Start date
R

Roy Goldhammer

Hello there

In short time i've started to unbound all my application to improve
preformance and to reduse the network transportation.

When i unbound combobox i've belt my own function that load combobox using
query with or without parameter.

The improve came fast and my problem now is that i use String object of vb
that in some times it's not enouth to have all the data on query. For
example i tried to load using the rowsource property query with 500 rows and
3 columns of 50 characters approx.

How can i use in this cases the unbound combobox?
 
Before you decided that you could do a better job of handling data than
Access itself, did you take a good look at the Performance section for
Access in a multiuser environment at MVP Tony Toews' site,
http://www.granite.ab.ca/accsmstr.htm?

You have to be very, very good at what you're doing, in general, to beat
Access at its own game (that is, using unbound forms and handling them with
your VBA code); and you're going to expend a great deal of time and effort
trying.

Because I have seen so many cases of people "unbinding" when they could have
done the work faster, easier, and gotten just as good or better performance
using bound forms and knowing how those bound forms work, I strongly
discourage using unbound forms unless there is clear and compelling need and
they have exhausted the numerous sources of performance improvement.

It appears you are using the ValueList and have run into its limit.

In a ComboBox with AutoExpand, you can handle somewhat more data, but the
recommended maxium for a Combo Box without AutoExpand is 20 - 50 items.
That's not because of software limitations but limitations of the humans who
have to use it and scroll through hundreds of items.

Perhaps you need to take a close look at the design of your user interface
here rather than worrying about how to exceed the limits.

Or, you could monitor what the user has typed, and load the Value List in
bits and pieces. Or, you could store that information temporarily in a local
table. Or, maybe someone else has a recommendation.


Larry Linson
Microsoft Access MVP
 
Back
Top